From: Sam Vilain <sam@vilain.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: Bryan Jacobs <bjacobs@woti.com>, git@vger.kernel.org
Subject: Re: [spf:guess] Re: [PATCH] Teach dcommit --mergeinfo to handle multiple lines
Date: Wed, 31 Aug 2011 21:40:35 -0700 [thread overview]
Message-ID: <4E5F0CC3.6020805@vilain.net> (raw)
In-Reply-To: <20110901013734.GA31207@dcvr.yhbt.net>
On 31/08/11 18:37, Eric Wong wrote:
> Sam Vilain <sam@vilain.net> wrote:
>> Ok, well I guess this is a useful intermediate feature then. Feel
>> free to copy in any further changes you may come up with in this
>> area to me, if you decide to do that.
> Shall I consider this an Acked-by?
Acked-by: Sam Vilain <sam@vilain.net>
Cheers,
Sam
prev parent reply other threads:[~2011-09-01 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 16:48 [PATCH] Teach dcommit --mergeinfo to handle multiple lines Bryan Jacobs
2011-08-31 20:21 ` Eric Wong
2011-08-31 20:43 ` [spf:guess] " Sam Vilain
2011-08-31 20:51 ` Bryan Jacobs
2011-08-31 22:15 ` [spf:guess,iffy] " Sam Vilain
2011-09-01 1:37 ` Eric Wong
2011-09-01 4:40 ` Sam Vilain [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=4E5F0CC3.6020805@vilain.net \
--to=sam@vilain.net \
--cc=bjacobs@woti.com \
--cc=git@vger.kernel.org \
--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).