[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: <kfogel_at_collab.net>
Date: 2004-02-12 17:23:23 CET

Dmitry Mikhin <dmitrym@acres.com.au> writes:
> The attached repo illustrates a problem with preserving log messages in
> cvs2svn conversion.
> The problem: the log is truncated if the file was removed in some revisions,
> then restored.

Hmmm... This is an interesting question.

When cvs2svn.py restores a file, it does a plain add, not an add with
history (if I recall correctly, & inspection of the code seems to bear
this out). It behaves this way because it doesn't have any way to
know if the reappearance of the file is a genuine resurrection -- that
is, related to the prior contents -- or just an add of new material
that happens to be under the same name as something that was removed
long ago.

We could have an option governing which way it chooses, though.

Before filing a 'cvs2svn-opt' issue, I want to make sure the problem
I'm describing is the same as the one you're describing. Does the
above all make sense to you?

> Minor problem (may be not a problem at all): cvs log shows when a file was
> initially added on a branch. The message is not available in svn repo upon
> conversion.

Doesn't the file appear in an SVN revision, which has a log message?
I'm not sure I understand the problem... Er, could you come up with a
very small example repository, containing just the minimal amount of
data needed to describe this problem? That would make it much easier
to understand, thanks.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 12 18:24:56 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.