Re[2]: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-23 Thread Ilya Basin
ESR> Ilya Basin : >> For new branches the 'from' command can refer the common ancestor in >> an existing branch. For example: >> >> /--E thebranch >> / >> A---B---C---D master >> >> Commit E is newer than D; we already imported D; thebranch is new. >> Instead of: >>

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-23 Thread Eric S. Raymond
Ilya Basin : > For new branches the 'from' command can refer the common ancestor in > an existing branch. For example: > > /--E thebranch > / > A---B---C---D master > > Commit E is newer than D; we already imported D; thebranch is new. > Instead of: > from refs/he

Re[2]: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-23 Thread Ilya Basin
>> But if the branch is new, but it's parent commit is already imported, >> I guess, the only way to refer it is by its SHA-1 >> Eric, what parent information can cvsps provide for the first commit >> in a branch, when invoked with the '-d' flag? ESR> At the moment it doesn't provide any at all.

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-23 Thread Eric S. Raymond
Apologies for the somewhat belated reply. I've been even busier than usual lately and am about to be traveling for a week. Ilya Basin : > Hi Eric. > > ESR> cvs-fast-export does not have incremental-import support. > ESR> Whether git-cvs-import has it depend on which version you have > ESR> and w

Re[2]: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-20 Thread Ilya Basin
Hi Eric. ESR> cvs-fast-export does not have incremental-import support. ESR> Whether git-cvs-import has it depend on which version you have ESR> and what backend it it is using. I don't maintain that wrapper. Did you mean "git-fast-import"? Or do you know any wrapper that already uses cvsps3 --fas

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-18 Thread Eric S. Raymond
Ilya Basin : > Hi Eric. > > I tried --fast-export. It's 2 times faster. > The first thing that differs: in cvsps2 commits with adjacent > timestamps were joined into one (see the attached files). Do you know > the reason? The cvsps guy included code to do that. Keith Packard didn't. Sorry I can

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-15 Thread Jakub Narębski
Ilya Basin wrote: > Does this --fast-export thing support what John mentioned, the > "incremental import support"? Does 'git fast-import' has it? > I need it, because full import takes too long. > > The central repo of my employer is CVS, other people commit to it and > I use git internally to be

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-15 Thread Ilya Basin
Hi Eric. I tried --fast-export. It's 2 times faster. The first thing that differs: in cvsps2 commits with adjacent timestamps were joined into one (see the attached files). Do you know the reason? Does this --fast-export thing support what John mentioned, the "incremental import support"? Does 'g

Re: State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-14 Thread Michael Haggerty
On 04/14/2013 01:33 PM, Eric S. Raymond wrote: > [...] > I wish I could point you at a convertor I really trust. I can't. > There is a third tool, cvs2git (based on the analyzer from cvs2svn) > that I don't maintain, which has problems of its own. ^

State of CVS-to-git conversion tools (Was: Re: cvsps: bad usage: invalid argument --norc)

2013-04-14 Thread Eric S. Raymond
Ilya Basin : > IB> Hi esr. > IB> In cvsps 3.10 the flag --norc was removed. It broke 'git cvsimport'. > IB> Please give the option back and write something in the man page like: > IB> This option has no effect; it is present for compatibility > > Looks like the tool is completely different. I