This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: switching kawa from cvs to svn?
- From: Nic James Ferrier <nferrier at tapsellferrier dot co dot uk>
- To: Per Bothner <per at bothner dot com>
- Cc: kawa at sourceware dot org
- Date: Thu, 18 May 2006 17:27:36 +0100
- Subject: Re: switching kawa from cvs to svn?
- References: <446C9B3A.8030801@bothner.com>
Per Bothner <per@bothner.com> writes:
> I'm thinking about converting Kawa's version-control system
> from CVS to Subversion (http://subversion.tigris.org/).
> Subversion (SVN) has various improvements over CVS (see the
> link), but of course it's not quite as ubiquitous. People
> who access the Kawa CVS tree would have to get a SVN client.
> If you use Eclipse, you have to get the "subclipse" plugin.
>
> The advantages would mainly be for me and the disadvantages
> mainly for you guys, but you would see some benefits: I'd
> be more eager to clean up the hierarchy by renaming classes,
> and I'll be better at tagging releases etc.
>
> I don't know what's involved in switching the repository
> (server), but as the "overseers" did this switch last year
> for gcc on the same host I assume I don't have to do much myself.
Maybe you should condider switching to darcs. IMHO it is much superior
to svn.
There is a tool called tailor which will sync a CVS repository with
darcs (or vice versa).
In fact tailor will sync just about anything with anything.
Nic