Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-25 Thread John Keeping
On Thu, Jan 24, 2013 at 10:55:57PM -0600, Chris Rorvick wrote: On Wed, Jan 23, 2013 at 3:12 PM, John Keeping j...@keeping.me.uk wrote: The existing script (git-cvsimport.perl) won't ever work with cvsps-3 since features it relies on have been removed. Not reporting the ancestry branch

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-24 Thread Chris Rorvick
On Wed, Jan 23, 2013 at 3:12 PM, John Keeping j...@keeping.me.uk wrote: The existing script (git-cvsimport.perl) won't ever work with cvsps-3 since features it relies on have been removed. Not reporting the ancestry branch seems to be the big one. Are there others? I had a version of the Perl

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread John Keeping
On Tue, Jan 22, 2013 at 04:11:59PM -0800, Junio C Hamano wrote: John Keeping j...@keeping.me.uk writes: Would you mind holding off on this? As it stands there are a couple of issues with the cvsimport-3 script including: ... Actually I do. I think this, at least the early part of it, should

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread Chris Rorvick
On Wed, Jan 23, 2013 at 3:28 AM, John Keeping j...@keeping.me.uk wrote: In my opinion the incremental import support really is substantially worse in cvsimport-3 than cvsimport-2. cvsimport-2 looks at the output of git-for-each-ref to calculate the dates from which to continue each branch.

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread John Keeping
On Wed, Jan 23, 2013 at 07:26:24AM -0600, Chris Rorvick wrote: On Wed, Jan 23, 2013 at 3:28 AM, John Keeping j...@keeping.me.uk wrote: In my opinion the incremental import support really is substantially worse in cvsimport-3 than cvsimport-2. cvsimport-2 looks at the output of

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread Junio C Hamano
John Keeping j...@keeping.me.uk writes: My preference would be for something like this, possibly with an expanded examples section showing how to pipe the output of cvsps-3 or cvs2git into git-fast-import: -- 8 -- diff --git a/Documentation/git-cvsimport.txt

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread John Keeping
On Wed, Jan 23, 2013 at 09:13:27AM -0800, Junio C Hamano wrote: John Keeping j...@keeping.me.uk writes: My preference would be for something like this, possibly with an expanded examples section showing how to pipe the output of cvsps-3 or cvs2git into git-fast-import: -- 8 --

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-23 Thread Junio C Hamano
John Keeping j...@keeping.me.uk writes: Is it it does not work yet with cvsps3, or it will not ever work with cvsps3? The impression I am getting is that it is the latter. The existing script (git-cvsimport.perl) won't ever work with cvsps-3 since features it relies on have been removed. I

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-22 Thread John Keeping
On Tue, Jan 22, 2013 at 02:44:48PM -0800, Junio C Hamano wrote: * jc/cvsimport-upgrade (2013-01-14) 8 commits - t9600: adjust for new cvsimport - t9600: further prepare for sharing - cvsimport-3: add a sample test - cvsimport: make tests reusable for cvsimport-3 - cvsimport: start

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

2013-01-22 Thread Junio C Hamano
John Keeping j...@keeping.me.uk writes: On Tue, Jan 22, 2013 at 02:44:48PM -0800, Junio C Hamano wrote: * jc/cvsimport-upgrade (2013-01-14) 8 commits - t9600: adjust for new cvsimport - t9600: further prepare for sharing - cvsimport-3: add a sample test - cvsimport: make tests reusable