Re: cvs2svn conversion directly to git ready for experimentation
Show 17 quoted lines
> Simon 'corecode' Schubert wrote:
>> Steffen Prohaska wrote:
>>> BTW, togit creates much more complex branching patterns than cvs2svn
>>> does. The attached file branching.png displays a small view of a
>>> branching pattern that extends downwards over a couple of screens.
>>> I checked the cvs2svn history again. It doesn't contain anything
>>> of similar complexity.
>> haha yea, there is still some issue with duplicate branch names and the
>> branchpoint. if it doesn't get the branch right, it will always "pull"
>> files from the parent branch.
>
> This sounds very much like the problem reported by Daniel Jacobowitz
> [1]. The problem is that if you create a branch A on a file, then
> create branch B from branch A before making a commit on branch A, then
> CVS doesn't record that branch A was the source of branch B. (It treats
> B as if it sprouted directly from the revision that was the *source* of
> branch A.) The same problem exists if "B" is a tag.
I think I have covered this case quite well. I believe "my" problem happens when there are files being copied manually within the repository and then branch names being changed (or just branch names being changed). However, the name change just happens only on a subset of files and branches, so you wind up with a commit which is part of two branches. Or something like that. I really should have the time to investigate this.
One elementary problem with CVS is that you can assign two branch names to the same branch. During conversion you need to choose one over the other.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Simon 'corecode' Schubert <corecode@fs.ei.tum.de>