From: Junio C Hamano <gitster@pobox.com>
To: "W. Trevor King" <wking@tremily.us>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2014, #09; Tue, 30)
Date: Tue, 30 Sep 2014 14:09:09 -0700 [thread overview]
Message-ID: <xmqqppecrf2i.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140930204704.GI3770@odin.tremily.us> (W. Trevor King's message of "Tue, 30 Sep 2014 13:47:05 -0700")
"W. Trevor King" <wking@tremily.us> writes:
> On Tue, Sep 30, 2014 at 01:23:18PM -0700, Junio C Hamano wrote:
>> Here are the topics that have been cooking.
>
> It looks like my boring git-mailinfo doc patch [1] fell through the
> cracks here ;). Or maybe it's just cooking a bit longer before
> getting queued?
Nobody is cooking it as far as I remember. Did I see any discussion
on it?
I looked at the new text and I find it fairly objectionable.
A review in a separate message will follow.
next prev parent reply other threads:[~2014-09-30 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 20:23 What's cooking in git.git (Sep 2014, #09; Tue, 30) Junio C Hamano
2014-09-30 20:47 ` W. Trevor King
2014-09-30 21:09 ` Junio C Hamano [this message]
2014-10-01 4:01 ` David Aguilar
2014-10-02 17:46 ` Junio C Hamano
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=xmqqppecrf2i.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wking@tremily.us \
/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).