From: Jeff King <peff@peff.net>
To: Eric <esr@thyrsus.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clarify how content states are to be built as the fast-import stream is interpreted.
Date: Thu, 8 Nov 2012 13:32:42 -0500 [thread overview]
Message-ID: <20121108183242.GA17950@sigill.intra.peff.net> (raw)
In-Reply-To: <20121108183038.GA4003@thyrsus.com>
On Thu, Nov 08, 2012 at 01:30:38PM -0500, Eric wrote:
> > Looks reasonable. Sign-off?
> >
>
> Ah, right. Shall resend with signoff. Probably Tuesday - I'm on the
> road, and the git instance on my laptop is prone to library-load issues.
>
> Or you can just add
>
> Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
That's fine. I can fix it up locally. Thanks.
-Peff
prev parent reply other threads:[~2012-11-08 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 4:31 [PATCH] Clarify how content states are to be built as the fast-import stream is interpreted Eric S. Raymond
2012-11-08 17:43 ` Jeff King
[not found] ` <20121108183038.GA4003@thyrsus.com>
2012-11-08 18:32 ` Jeff King [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=20121108183242.GA17950@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
/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).