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

Re: cvs2svn: log conversion

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-02-25 01:58:00 CET

On Mon, 2004-02-23 at 15:39, Jack Repenning wrote:
> > Should CVS users see one behavior on the data they
> > had in their CVS repositories, and another behavior on data they have
> > created since?

> Well, should CVS users see one behavior on the data they committed
> before the conversion, and a different behavior on the same data after
> conversion?

Sure, if Subversion behaves differently. For instance, if I run "cvs
log" on a file in my working copy, I see commits which are more recent
than my working directory, but "svn log" only shows me commits which are
older than my working copy.

Similarly, the normal behavior of "cvs log" is to show information about
every file which has occupied a pathname, while the normal behavior of
"svn log" is to show information about one file. We have tried to keep
the operational differences between CVS and SVN to a minimum, but we'd
have to give up directory versioning completely to eliminate them
entirely. Hacking up converted CVS repositories in order to smooth over
some tiny aspect of the transition does not seem like a good long-term
strategy.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 25 02:05:24 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.