From: Michael Olson <mwolson@gnu.org>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>,
Michael J Gruber <git@drmicha.warpmail.net>,
Tim Stoakes <tim@stoakes.net>
Subject: Re: [spf:guess,iffy,mismatch] Re: [PATCH/RFC 2/2] git-svn: Don't allow missing commit parent to stop git-svn
Date: Wed, 28 Apr 2010 08:51:12 -0700 [thread overview]
Message-ID: <r2jc8b3bef91004280851i865a911ei47b1be606dd560d9@mail.gmail.com> (raw)
In-Reply-To: <4BCF8E07.9080507@vilain.net>
On Wed, Apr 21, 2010 at 4:45 PM, Sam Vilain <sam@vilain.net> wrote:
> Michael Olson wrote:
>> Interestingly, I see people reporting the same problem in the thread
>> "git svn clone of subversion's own code failing". So it's not just
>> related to patch 1/2 of this series. At least that thread has a
>> public-facing repo so the problem should be easier to reproduce for
>> a real fix.
>
> Oh, right ... I remember that issue now. I'm currently testing the
> below change to see if it breaks the test suite; any issues and I'll
> post an update.
>
> Subject: [PATCH] git-svn: deal with svn cherry-picks with non-linear history
>
> The expression 'BASE^..TIP' is only defined when BASE has parents. It
> actually does what it intends only when it has one parent.
>
> Allow for more complicated revision list arguments than a range by
> splitting any space-containing arguments on the way into _rev_list,
> and check the parents of the bottom commit so that we may use the
> correct revision list specifier.
> ---
> git-svn.perl | 22 +++++++++++++++++++---
> 1 files changed, 19 insertions(+), 3 deletions(-)
>
> [snip]
This change works great on my private repos, so it should supersede my
version which only did an eval.
--
Michael Olson | http://mwolson.org/
next prev parent reply other threads:[~2010-04-28 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 21:30 [PATCH/RFC 2/2] git-svn: Don't allow missing commit parent to stop git-svn Michael Olson
2010-04-21 20:07 ` Sam Vilain
2010-04-21 21:17 ` Michael Olson
2010-04-21 23:45 ` [spf:guess,iffy,mismatch] " Sam Vilain
2010-04-28 15:51 ` Michael Olson [this message]
2010-05-03 21:19 ` Eric Wong
2010-05-04 6:40 ` Michael J Gruber
2010-05-04 18:34 ` Eric Wong
2010-05-04 22:02 ` Sam Vilain
2010-05-04 23:16 ` Eric Wong
2010-05-19 21:17 ` Michael Olson
2010-05-19 21:19 ` Michael Olson
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=r2jc8b3bef91004280851i865a911ei47b1be606dd560d9@mail.gmail.com \
--to=mwolson@gnu.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=sam@vilain.net \
--cc=tim@stoakes.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).