From: Junio C Hamano <gitster@pobox.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2019, #01; Mon, 2)
Date: Wed, 04 Dec 2019 10:14:58 -0800 [thread overview]
Message-ID: <xmqqwobc3ql9.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191204061917.GB3381576@generichostname> (Denton Liu's message of "Tue, 3 Dec 2019 22:19:17 -0800")
Denton Liu <liu.denton@gmail.com> writes:
> On Tue, Dec 03, 2019 at 08:38:47AM -0800, Junio C Hamano wrote:
>> Denton Liu <liu.denton@gmail.com> writes:
>>
>> > René sent a v2 for the above commit here[2].
>> > ...
>> > [2]: https://lore.kernel.org/git/a56a4b33-61f8-d3a5-d85f-431c70b8f3e7@web.de/
>>
>> That is what has become ed254710 ("test: use test_must_be_empty F
>> instead of test_cmp empty F", 2019-11-27), I think.
>
> Hmm, perhaps it was human error on my part but I was pretty sure that I
> saw the `PIPE` when I was looking at the branch on GitHub. Maybe there
> was some issue related to whatever Elijah was experiencing earlier as
> well?
>
> Anyway, double-checking now, that commit looks correct to me. Sorry for
> the false alarm.
Thanks for checking. Better to see occasional false alarms to
make me double check than letting mistakes fall through the cracks.
next prev parent reply other threads:[~2019-12-04 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 14:16 What's cooking in git.git (Dec 2019, #01; Mon, 2) Junio C Hamano
2019-12-02 15:59 ` Elijah Newren
2019-12-02 21:05 ` Denton Liu
2019-12-03 16:34 ` Junio C Hamano
2019-12-03 16:38 ` Junio C Hamano
2019-12-04 6:19 ` Denton Liu
2019-12-04 18:14 ` Junio C Hamano [this message]
2019-12-04 18:53 ` Derrick Stolee
2019-12-06 21:31 ` Junio C Hamano
2019-12-13 13:38 ` Ed Maste
2019-12-13 13:58 ` Ed Maste
2019-12-13 19:02 ` Junio C Hamano
2019-12-16 2:26 ` Heba Waly
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwobc3ql9.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).