Hi Aaron,
>There are many cases in which the CVS source currently fails to export
>tags. Some of them reflect fundamental limitations of CVS and would be
>very expensive or perhaps impossible to solve, but others could probably
>be worked around.
I deeply agree cvs does not help. cvsps does extract most tags, but
occasionally gets them wrong, even if it reports them as "funky" or
"invalid" - I'm aware that git-cvsimport, relying on cvsps, is not
guaranted to migrate them correctly.
If you're talking about the "funky" case, then a simple reordering of
patchsets can solve the problem. If you're talking about "invalid" ones,
then I think they can be solved by creating a new patchset, whose
ancestors are all latest patchsets which contain the tagged revisions
(maybe falling back to a single one for those scm's not able to record
such merges, but even for those a native idiom can surely be found).
But in either case, I agree it is not trivial to do with only plain cvs.
That would surely be easier with cvsps.
But maybe you're talking about a different classification ?
> If you can make the test repo available, I may or may
>not be able to fix the problem for that repo, and in any case I'd be
>interested to see if this is one of the cases I already know about, or
>if it's a new one.
The repo is on savannah, see the tailor config in my orig mail for details.
Best regards,
--
Yann Dirson <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
