From: "Eric S. Raymond" <esr@thyrsus•com>
To: John Keeping <john@keeping•me.uk>
Cc: git@vger•kernel.org
Subject: Re: git-cvsimport-3 and incremental imports
Date: Sun, 20 Jan 2013 18:20:08 -0500 [thread overview]
Message-ID: <20130120232008.GA25001@thyrsus.com> (raw)
In-Reply-To: <20130120200922.GC7498@serenity.lan>
John Keeping <john@keeping•me.uk>:
> I don't think there is any way to solve this without giving cvsps more
> information, probably the last commit time for all git branches, but
> perhaps I'm missing a fast-import feature that can help solve this
> problem.
Yes, you are. The magic incantation is
from refs/heads/<branch>^0
I've just pushed a cvsps-3.9 with an -i option that generates these at
each branch root. Combine it with -d and you get incremental
fast-export.
You get to integrate this. I think the transition strategy Junio
has chosen is seriously mistaken, leading to unnecessary grief for users
who will be fooled into thinking it's OK to still use cvsps-2.x. Because
I do not wish to encourage or endorse this mistake and am tired of arguing
against stubborn determination to do the wrong thing, I am not going to
sink more effort into the git project's end of the CVS-lifting problem.
There are too many better uses for my time.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2013-01-20 23:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 20:09 git-cvsimport-3 and incremental imports John Keeping
2013-01-20 23:20 ` Eric S. Raymond [this message]
2013-01-20 23:34 ` Jonathan Nieder
2013-01-21 0:01 ` Junio C Hamano
2013-01-21 0:06 ` Junio C Hamano
2013-01-20 23:42 ` Jonathan Nieder
2013-01-21 1:06 ` Eric S. Raymond
2013-01-21 6:42 ` Jonathan Nieder
2013-01-21 7:28 ` Junio C Hamano
2013-01-21 7:35 ` Junio C Hamano
2013-01-21 9:36 ` John Keeping
2013-01-21 11:28 ` Eric S. Raymond
2013-01-21 12:00 ` John Keeping
2013-01-21 12:43 ` Eric S. Raymond
2013-01-21 13:27 ` John Keeping
2013-01-21 14:07 ` Eric S. Raymond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130120232008.GA25001@thyrsus.com \
--to=esr@thyrsus$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=john@keeping$(echo .)me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox