[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Fix to cvs2svn.py -p option for 1.0

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-01-07 22:29:25 CET

Roland Dreier wrote:
> I think that my tiny patch to cvs2svn.py (which moves the
> initialization of start_pass to the correct place in the script)
> should probably be committed to the 1.0-stabilization branch. (It was
> committed to trunk as revision 8166)
> Without the patch, the -p option of cvs2svn.py is completely broken,
> and the patch is "low risk" and "totally obvious" (famous last words,
> I know, but in this case I think it's true).

I guess its time to sort out a consensus about cvs2svn and 1.0.

If you look at the issue tracker, you will be able to see that there are
important defects to be resolved before cvs2svn can be considered 1.0.

cvs2svn simply isn't close enough to 1.0 for the whole STATUS/3
votes/stabilization thing to be workable. I believe most, if not all,
cvs2svn changes on the trunk will need application to the branch - either
because they are small, or because they are complex but fix important bugs.

In other words, it will likely be appropriate to copy cvs2svn from the trunk
to the 1.0 branch.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 7 22:30:16 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.