Re: [Issue 875] Changed - cvs2svn combines separate commits (?)

Martin Tomes wrote:
> Scott Lamb wrote:
>
>> issues@subversion.tigris.org wrote:
>>
>>> http://subversion.tigris.org/issues/show_bug.cgi?id=875
>>
>>
>> It definitely is not okay for me. cvs2svn.py is combining commits by
>> the same author and five-minute span with different commit messages.
>> In some cases, these are two revisions of the _same_file_. (Correcting
>> some obvious error in an earlier commit, for instance.)
>
>
> I use an MD5 checksum of the commit message plus the date of the commit
> which to identify a set of files commited together. It fails when
> someone commits the same fix to several branches of the same file and
> uses the same commit text, but this is a rare occurance and is
> detectable, I just haven't got round to fixing it.

This was a simple case with no branches and distinct log messages. It
gives output like this:

     committing: Wed Jul 3 21:02:50 2002, over 193 seconds
         changing 1.13 : /reps/form/reps.fmb
         changing 1.14 : /reps/form/logs.fmb
         changing 1.15 : /reps/form/logs.fmb
         (skipped; dry run enabled)

And in cvs2svn-data.revs, those two revisions have different checksums:

     3d23ad8b c4b3020b30299a53a468809e9ad7e6e761a74b7b C 1.15
/home/cvs/root/reps/form/logs.fmb,v
     3d23acca 759967f3f3ce5a6d5a6604897c4fb5b63717d889 C 1.14
/home/cvs/root/reps/form/logs.fmb,v

I can pull data from the other cvs2svn-data.* files. Afraid I don't
really understand the significance of all the slightly-different files.

-- 
Scott Lamb
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org