J.M. Maurer wrote:
>
> There are several reasons why we want to make the change, such as:
>
> - Commits are atomic
> - Directories, renames, and file meta-data are versioned
> - Move efficient than cvs, bandthwidth wise
> - Per commit version numbers, as opposed to per file (YAY!)
> - cvs is 'dead' (although a new project has setup to continue, cvsnt)
This reads more like a list of why SVN is better than CVS in general
rather than why SVN is better than CVS for AbiWord. The bandwidth reason
seems weak too, considering the recent switch away from SourceForge.
>
> For a start, I switched over some cvs modules to subversion. No-one
> except the system admins are affected by this change. We will test out
> the current setup, and if it satisfies our needs, we will switch over
> all our cvs repositories (the complete cvs history will be migrated too,
> so we don't loose valuable information). Of course, such a change would
> be announced weeks in advance.
_With some difficulty_ the modules got switched over (i.e. footnote two
from your email), which makes me question the non-trivial time
investment it will take to switch over everything completely.
>
> Note that noting is set in stone, and everything is freely debatable.
I'm not in favor of the transition from CVS to SVN. For one, I've just
started to get the hang of CVS :), and would rather not have to spend
time learning a new system and program. I'm also having a hard time
seeing the point of investing time in changing something that seems to
work fine already (not just my time, mind you, but everyone's). Just my
two cents on the matter, though.
Received on Fri Apr 8 05:48:52 2005
This archive was generated by hypermail 2.1.8 : Fri Apr 08 2005 - 05:48:53 CEST