From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2019, #04; Tue, 17)
Date: Wed, 18 Dec 2019 14:40:05 -0800 [thread overview]
Message-ID: <xmqqa77pcl6i.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BEyNcJPp0BSPLiAYpmCMLWcqiQQc5GZnhahbCez2vyqzQ@mail.gmail.com> (Elijah Newren's message of "Wed, 18 Dec 2019 11:33:04 -0800")
Elijah Newren <newren@gmail.com> writes:
> On Tue, Dec 17, 2019 at 2:03 PM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Here are the topics that have been cooking. Commits prefixed with
>> '-' are only in 'pu' (proposed updates) while commits prefixed with
>> '+' are in 'next'. The ones marked with '.' do not appear in any of
>> the integration branches, but I am still holding onto them.
>>
> ...
>> [New Topics]
>
> It appears that
> https://lore.kernel.org/git/2d1f9a8485e744e23b1f02826877afe829a639cf.1576271025.git.gitgitgadget@gmail.com/
> from last Friday may have fallen through the cracks. Could that one
> be picked up?
Indeed. I was quite sure that I picked up a "merge made a known
breakage go away---this should have been done as an evil merge, but
it wasn't, so here is a late fix" patch, but I apparently didn't.
Thanks.
next prev parent reply other threads:[~2019-12-18 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 22:00 What's cooking in git.git (Dec 2019, #04; Tue, 17) Junio C Hamano
2019-12-18 17:15 ` Elijah Newren
2019-12-18 18:01 ` Junio C Hamano
2019-12-18 19:33 ` Elijah Newren
2019-12-18 22:40 ` Junio C Hamano [this message]
2019-12-19 14:56 ` Pratyush Yadav
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=xmqqa77pcl6i.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@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).