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

Re: [Issue 1105] Changed - cvs2svn doesn't respect executable bit

From: <kfogel_at_newton.ch.collab.net>
Date: 2003-01-24 17:57:47 CET

Greg Stein gstein@lyra.org writes:
  + cvs2svn issues don't block Subversion 1.0, so they go in Post-1.0,
  + where resides the master cvs2svn issue, issue #514.
 Hunh? How can we ship svn without a converter? Our entire purpose is
 to replace CVS.

We're already shipping svn without a converter :-).

Could also ask, why wasn't this a big deal before now? We've been
tossing cvs2svn issues into Post-1.0 for ages, starting with the
original issue #514. This is nothing new. But probably you just
didn't notice, or you would have asked earlier...

I completely agree that cvs2svn is important. But the ability to
convert a particular versioned datastore to Subversion is unrelated to
Subversion's own readiness for use. Subversion could be bug-free and
have first-class changeset support... Would we then say Oh, it's not
1.0 yet, because we don't have a tool to convert CVS repositories.?
What about all those people starting new projects? It's not 1.0 for
them? Sure it is.

Maybe the real problem is that we have this milestone label Post-1.0
that we use to mean two different things:

   1. This is a Subversion bug, but it need not block a 1.0 release.

   2. This bug isn't really about Subversion, so it need not block a
       1.0 release.

We could start using the `inapplicable' milestone for category (2), or
use some new nomenclature, if we can think of something clearer.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:13:59 2006

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.