Re: Since there's a resurgence of interest in cvs2svn...

Shun-ichi GOTO wrote:

> 1) This means changes in a.c:1.4 are not recorded in
> svn repository. Is it acceptable?

No

> 2) For branching support patch,
>
> If cvs repository have tag with a.c:1.4 and b.c:1.2, this grouping
> (by cvs2svn.py r3446) whould prevents right tagging because revision
> 3 only has b.c and revision 2 doesn't have a.c:1.4.
> For correct tagging, I think we should not add new revision to commit
> group if same file is already added and it have tag. And we should

Yes

> not add another file to commit group, which have different tag agaist
> tag in group. In other word, we should keep commit group as no tag
> or one tag at most.

This last issue is not a problem at all. Any given CVS file revision can
have any number of tags. There are also no ordering constaints for the
tags on different files. You can easily tag a current version of file A
and an older version file B with the same tag (and then even proceed to
branch from that). My code seems to handle it fine.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 23 07:30:38 2002