From: Michael J Gruber <git@drmicha•warpmail.net>
To: Eric Wong <normalperson@yhbt•net>
Cc: Michael Olson <mwolson@gnu•org>, Sam Vilain <sam@vilain•net>,
git@vger•kernel.org, Tim Stoakes <tim@stoakes•net>
Subject: Re: [PATCH/RFC 2/2] git-svn: Don't allow missing commit parent to stop git-svn
Date: Tue, 04 May 2010 08:40:49 +0200 [thread overview]
Message-ID: <4BDFC171.5010103@drmicha.warpmail.net> (raw)
In-Reply-To: <20100503211942.GA1380@dcvr.yhbt.net>
Eric Wong venit, vidit, dixit 03.05.2010 23:19:
> Michael Olson <mwolson@gnu•org> wrote:
>> 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
>>
>> This change works great on my private repos, so it should supersede my
>> version which only did an eval.
>
> Have either of you had a chance to look into the test suite breakage
> from this patch? Thanks.
>
Uhm, which one: The one in your subject line or the one in the quoted
subject line?
Michael
next prev parent reply other threads:[~2010-05-04 6:41 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
2010-05-03 21:19 ` Eric Wong
2010-05-04 6:40 ` Michael J Gruber [this message]
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=4BDFC171.5010103@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=mwolson@gnu$(echo .)org \
--cc=normalperson@yhbt$(echo .)net \
--cc=sam@vilain$(echo .)net \
--cc=tim@stoakes$(echo .)net \
/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