SVN project spreading FUD about cvs2svn? :-)

[Michael Haggerty <mh...@alum.mit.edu>]

I just noticed what the Subversion FAQ has to say about cvs2svn:

> Members of the Subversion development community created and maintain
> a tool called cvs2svn. You can find it at http://cvs2svn.tigris.org/.
> Be sure to read the cvs2svn documentation.
> 
> If cvs2svn.py does not work for you, (e.g. your repository causes it
> to crash, or it doesn't deal with branches and tags quite how you would
> like), there are at least two other conversion utilities you can try.
> These have different features (and possibly different bugs):
> [...]

This makes unflattering implications about cvs2svn that are also IMHO no
longer warranted.  The comment was probably fair WRT earlier versions of
cvs2svn, which were more unstable.  But I think that cvs2svn 2.x is
quite robust, reliable, and flexible.

Is there a sympathetic soul who would be willing to change the FAQ?  If
you haven't followed the cvs2svn project, consider looking over the list
of current features [1].

Michael

[1] http://cvs2svn.tigris.org/features.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: SVN project spreading FUD about cvs2svn? :-)

[Karl Fogel <kf...@red-bean.com>]

Michael Haggerty <mh...@alum.mit.edu> writes:
> I just noticed what the Subversion FAQ has to say about cvs2svn:
>
>> Members of the Subversion development community created and maintain
>> a tool called cvs2svn. You can find it at http://cvs2svn.tigris.org/.
>> Be sure to read the cvs2svn documentation.
>> 
>> If cvs2svn.py does not work for you, (e.g. your repository causes it
>> to crash, or it doesn't deal with branches and tags quite how you would
>> like), there are at least two other conversion utilities you can try.
>> These have different features (and possibly different bugs):
>> [...]
>
> This makes unflattering implications about cvs2svn that are also IMHO no
> longer warranted.  The comment was probably fair WRT earlier versions of
> cvs2svn, which were more unstable.  But I think that cvs2svn 2.x is
> quite robust, reliable, and flexible.
>
> Is there a sympathetic soul who would be willing to change the FAQ?  If
> you haven't followed the cvs2svn project, consider looking over the list
> of current features [1].

Done in r29407 and r29408, thanks for the suggestion!  (It's fine if
you want to just edit that FAQ entry yourself anytime, by the way.)

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org