Can cvs2hg "backdate" fixup tags?
Keith Refson
Keith.Refson at stfc.ac.uk
Sun Dec 18 14:20:05 UTC 2011
I am in the process of converting a much-branched CVS repository to
Mercurial using cvs2hg, and attempting to generate a Mercurial
repository which looks fairly clean for future development.
One problem I am running into, is that cvs2hg is generating artificial
changesets to close "fixup heads". These changesets are given a
Mercurial sequence number at the top, and a timestamp which is the date
of conversion. This means that my Mercurial repository contains recent
commits on old, and abandoned ex-CVS branches - sometimes years old.
These show up as mysteriously revivified old branches in GUI tools such
as "hg view" and tortoisehg.
Is there any way to convince cvs2hg to backdate these "close fixup head"
changesets to just after the last real commit on that branch? The idea
would be to put these artificial closes "out of sight"
In a similar vein, is there any way of backdating "close branch"
operations during the conversion to mark old CVS branches as inactive?
I want to leave these branches to be available for retrieval if
necessary, but ignore them most of the time. As with
the "close fixup heads" commits, just closing in Mercurial has the
unwanted effect of generating new activity on dead branches.
Keith Refson
--
Scanned by iCritical.
More information about the Mercurial
mailing list