Re: cvs2git: One possible bug, and two other issues

On Sun, Jan 9, 2011 at 3:02 AM, Michael Haggerty <[email protected]> wrote:
> On 01/03/2011 03:48 PM, Anders Pilegaard wrote:
>> Issue 3 - Allow selected tags to "expand" to cover more files
>> -------------------------------------------------------------
>> [...]
>> In our CVS repository we normally tag bugfixes with "before" and
>> "after" tags, to make it easier to apply them to another branch later
>> on.  Mostly we let those tags cover the entire repository.  But
>> sometimes - especially when the commit changes only a few files - we
>> just tag the affected files.
>> [...]
>> But this was not the intention of those tags - they were meant to
>> attach to specific commits.  And they do tag the files actually
>> changed in the commit - just not all the files in the repository.
>>
>> So I added some more code to allow certain tags to pass the
>> "is_simple_copy" test [...]
>
> I like this idea.  I guess that this practice is pretty common,
> especially considering how expensive it is to make a repository-wide tag
> in a big CVS repository.

Note that I addressed this in cvs2hg with the notion of "sloppy" and
"optional" fixup commits.  See
http://hg.gerg.ca/cvs2svn/raw-file/tip/README.cvs2hg under "Avoiding
fixup commits".

IIRC, the relevant code is in hg_output_option.py, around
_need_fixup() and _create_first_fixup().

Greg

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2697284

To unsubscribe from this discussion, e-mail: [[email protected]].