From: Junio C Hamano <gitster@pobox.com>
To: Leon George <leon@georgemail.eu>
Cc: git@vger.kernel.org, Brandon Williams <bmwill@google.com>
Subject: Re: slightly confusing message
Date: Mon, 20 Feb 2017 18:22:51 -0800 [thread overview]
Message-ID: <xmqq8tp0i8p0.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <8e66c3be-7cd9-d72c-123f-308b63ddc1bd@georgemail.eu> (Leon George's message of "Tue, 21 Feb 2017 03:15:07 +0100")
Leon George <leon@georgemail.eu> writes:
> On 20/02/17 21:19, Junio C Hamano wrote:
>> This sounds vaguely familiar and indeed I think it is this one:
>> https://public-inbox.org/git/CAEnOLdvG=SoKFxeJ_pLmamGj_8osC+28TSg+pbFLLTr+ZLcpQA@mail.gmail.com/
>> which was from late last year.
> Which means I should have found it before bothering you.
It means no such thing, though. It just means that I happen to be
more familiar with what has gone on the development recently than
you were ;-)
>> I suspect that the issue may already be fixed at the tip of 'master'
>> (aka Git 2.12-rc2).
> You're absolutely right. Took a while to build, but here goes:
> ...
> Splendid!
Thanks for confirming.
prev parent reply other threads:[~2017-02-21 2:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 12:35 slightly confusing message Leon George
2017-02-20 20:19 ` Junio C Hamano
2017-02-21 2:15 ` Leon George
2017-02-21 2:22 ` 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=xmqq8tp0i8p0.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=leon@georgemail.eu \
/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