Re: cvs2svn conversion directly to git ready for experimentation

On Aug 3, 2007, at 12:50 AM, Simon 'corecode' Schubert wrote:

Steffen Prohaska wrote:

quoted

quoted

yah, that pretty much tells me it is shawn's bug :)  but without  
more details, it is very hard to diagnose.

I tried again. Interestingly now togit works but tohg still fails.
togit starts with reporting
fatal: Not a valid object name

that's fine.

Looks a bit scary. Could you hide the message from the user
if it's fine.

quoted

as the first line. But besides that it seems to work fine. What
concerns me a bit is that the last line togit reports is
committing set 18100/18173
I'd expect it should report 18173/18173.

that's fine as well.  You only saw multiples of 100, but you didn't  
consider it would skip the itermediate ones, right? :)

I don't care about the intermediates, but only about the
last one. I'd expect that a successful import would report
as the last line 18173/18173. If the first number is smaller
than the second, this indicates to me that there's something
left to do.

quoted

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.

did you do some manual RCS file copying or manual branch name  
changing of individual files?  this could be the reason.  I still  
have to find a simple repo to reproduce this.

Maybe, the repo is 8 years old. It started before I joined the
development.

	Steffen