From: Junio C Hamano <gitster@pobox•com>
To: Ben Peart <Ben.Peart@microsoft•com>
Cc: Alex Vandiver <alexmv@dropbox•com>,
"git\@vger.kernel.org" <git@vger•kernel.org>
Subject: Re: What's cooking in git.git (Nov 2017, #05; Fri, 17)
Date: Tue, 21 Nov 2017 09:21:09 +0900 [thread overview]
Message-ID: <xmqqmv3glbwq.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <MWHPR21MB047824EDFD7AE4EC39256E7FF4220@MWHPR21MB0478.namprd21.prod.outlook.com> (Ben Peart's message of "Mon, 20 Nov 2017 13:49:24 +0000")
Ben Peart <Ben.Peart@microsoft•com> writes:
> As far as I can tell, the patches are good. I'm not aware of
> anything else that should hold it up.
Great; thanks.
prev parent reply other threads:[~2017-11-21 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 6:12 What's cooking in git.git (Nov 2017, #05; Fri, 17) Junio C Hamano
2017-11-17 6:35 ` Junio C Hamano
2017-11-20 13:49 ` Ben Peart
2017-11-21 0:21 ` Junio C Hamano [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=xmqqmv3glbwq.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=Ben.Peart@microsoft$(echo .)com \
--cc=alexmv@dropbox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/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