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: Mon, 21 Jan 2013 09:07:19 -0500 [thread overview]
Message-ID: <20130121140719.GA1409@thyrsus.com> (raw)
In-Reply-To: <20130121132706.GF7498@serenity.lan>
John Keeping <john@keeping.me.uk>:
> > Ah. OK, that is yet another bug inherited from 2.x - the code doesn't
> > match the documented (and correct) behavior. Please send me a patch
> > against the cvsps repo, I'll merge it.
>
> Should now be in your inbox.
Received, merged, tested, and cvsps-3.10 has shipped.
> I think the only way to do it without needing to save local state in the
> Git repository would be to teach cvsps to read a table of refs and times
> from its stdin so that we could do something like:
>
> git for-each-ref --format='%(refname)%09%(*authordate:raw)' refs/heads/ |
> cvsps -i --branch-times-from-stdin |
> git fast-import
>
> Then cvsps could create a hash table from this and use that to decide
> whether a patch set is interesting or not.
Agreed. I considered implementing something quite this before thinking of
the ^0 hack. But an out-of-band timestamp file is much simpler.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2013-01-21 14:08 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
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 [this message]
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=20130121140719.GA1409@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.