> From: Swen Thuemmler [mailto:swen@mediaways.net]
> Sent: 19 July 2002 13:00
> Hi all,
>
> when playing with cvs2svn.py I had some problems with the handling of
> CVS log messages. Only the last message of a changeset was incorporated
> in the svn commit. The enclosed patch fixes this. Now each log message
> from CVS is logged in Subversion together with the affected files (there
> might be the same message for some files and a different message for
> some other files). Additionally, the files get markers to be able to
> see whether it was a deletion, addition or modification.
>
> For example:
>
> M create.sql (1.2)
> M foo.c (1.4)
> A bar.c (1.1)
> M lib/tools.c (1.3)
> funny logmessage
> D context.sql (1.2)
> D drop.sql (1.2)
> No longer needed
> A sink.sql (1.1)
> Here is all the hot stuff
>
> This is probably a horrible hack for any decent python programmer (it is my
> first python code), and there might be better ways to implement this, but
> it does at least work. It would be nice, when some variation of this patch
> could get committed. I think it is important not to lose the version history when
> switching from CVS to Subversion.
>
> Comments?
Question: How do you determine if multiple commits are in the same changeset when
their commit msg differs? I mean, mostly a cvs commit of multiple files will have
the same commit msg. When are the commit msgs ever different _and_ still detectably
in the same changeset?
> --Swen
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 19 14:56:06 2002