From: Deskin Miller <deskinm@umich.edu>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net, gitster@pobox.com
Subject: Re: [PATCH] git-svn: Make following parents atomic
Date: Sun, 7 Dec 2008 17:24:44 -0500 [thread overview]
Message-ID: <20081207222444.GA10881@euler> (raw)
In-Reply-To: <1228665970-21204-1-git-send-email-deskinm@umich.edu>
On Sun, Dec 07, 2008 at 11:06:10AM -0500, Deskin Miller wrote:
> [...]
>
> To fix this, when we initialise the Git::SVN object $gs to search for
> and perhaps fetch history, we check if there are any commits in SVN in
> the range between the current revision $gs is at, and the top revision
> for which we were asked to fill history. If there are commits we're
> missing in that range, we continue the fetch from the current revision
> to the top, properly getting all history before using it as the parent
> for the branch we're trying to create.
On looking at the patch again, I think I might have introduced a bug:
it'll take the most commit on the parent branch, even if it was branched
from an earlier point. I'll spend more time looking at it and should
have a v2 in a day at most if I'm rigth, hopefully more like a few
hours.
Deskin Miller
next prev parent reply other threads:[~2008-12-07 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 16:06 [PATCH] git-svn: Make following parents atomic Deskin Miller
2008-12-07 16:10 ` [ANNOUNCE] git-svn-bugfix script (Re: [PATCH] git-svn: Make following parents atomic) Deskin Miller
2008-12-07 22:24 ` Deskin Miller [this message]
2008-12-08 6:20 ` [PATCH v2] git-svn: Make following parents atomic Deskin Miller
2008-12-08 8:33 ` Junio C Hamano
2008-12-08 13:31 ` [PATCH v3] " Deskin Miller
2008-12-08 23:35 ` Eric Wong
2008-12-16 13:22 ` Thomas Jarosch
2008-12-22 8:41 ` Thomas Jarosch
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=20081207222444.GA10881@euler \
--to=deskinm@umich.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).