From: Sam Vilain <sam@vilain.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>,
Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH/RFC 2/2] git-svn: Don't allow missing commit parent to stop git-svn
Date: Wed, 05 May 2010 10:02:35 +1200 [thread overview]
Message-ID: <1273010555.20723.17.camel@denix> (raw)
In-Reply-To: <20100504183452.GA30894@dcvr.yhbt.net>
On Tue, 2010-05-04 at 18:34 +0000, Eric Wong wrote:
> Michael J Gruber <git@drmicha.warpmail.net> wrote:
> > Uhm, which one: The one in your subject line or the one in the quoted
> > subject line?
>
> Sam's patch:
> Subject: [PATCH] git-svn: deal with svn cherry-picks with non-linear history
>
> Where he said:
> > >>> 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.
>
> Sorry for the confusion
Sorry for not following up - it didn't cause any test suite breakages
when I tested it. Especially if Michael has had joy with it I'd say
it's good to go...
Sam
next prev parent reply other threads:[~2010-05-04 22:03 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
2010-05-04 18:34 ` Eric Wong
2010-05-04 22:02 ` Sam Vilain [this message]
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=1273010555.20723.17.camel@denix \
--to=sam@vilain.net \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=mwolson@gnu.org \
--cc=normalperson@yhbt.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).