[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: <kfogel_at_collab.net>
Date: 2004-01-08 20:04:58 CET

Eric Gillespie <epg@pretzelnet.org> writes:
> I'm sure the previous posters will correct me if i misrepresent
> them, but that's exactly what i see them advocating. I don't
> want to see Subversion 1.0 held up waiting for cvs2svn, but i
> also don't want it to ship with an old cvs2svn. Subversion 1.0
> should include the best cvs2svn we have, from the trunk.

Oh. Let's see what state it's in then, yes. We'll want to ship with
either the latest trunk cvs2svn, or none at all, agree.

> This seems to be a recurring trend in these 1.0 discussions :).
> Subversion ships with some side projects that are not maintained
> on the same schedule, and sometimes not even by the same people.
> Subversion itself has a certain set of requirements for its 1.0
> release, and holding the bindings or cvs2svn to these
> requirements is not constructive.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 8 20:59:05 2004

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