From: Junio C Hamano <gitster@pobox.com>
To: Linus Arver <linusa@google.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #09; Tue, 27)
Date: Fri, 01 Mar 2024 08:16:01 -0800 [thread overview]
Message-ID: <xmqqsf1a7wse.fsf@gitster.g> (raw)
In-Reply-To: <xmqq1q8ubtg6.fsf@gitster.g> (Junio C. Hamano's message of "Thu, 29 Feb 2024 18:02:17 -0800")
Junio C Hamano <gitster@pobox.com> writes:
>> Doh, please wait for my v6 reroll (will send to the list in the next
>> half hour) to clean up the commit messages. Thanks.
>
> If we had communication gap and the topic was prematurely merged and
> was caught within a day or two, I would be a bit more sympathetic,
> but given that this was merged more than a week ago, that's totally
> unacceptable.
>
> If you have improvements, please do so as incremental patches on
> top. I'll hold the topic in 'next' until we are ready.
Well, I changed my mind. As we haven't rewound the tip of 'next'
post release, let's eject what is in 'next' and queue the latest,
pretending that the earlier round weren't in 'next' at all.
Thanks.
next prev parent reply other threads:[~2024-03-01 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 5:44 What's cooking in git.git (Feb 2024, #09; Tue, 27) Junio C Hamano
2024-02-28 13:38 ` Philippe Blain
2024-02-28 17:25 ` Junio C Hamano
2024-02-29 23:56 ` Linus Arver
2024-03-01 2:02 ` Junio C Hamano
2024-03-01 16:16 ` Junio C Hamano [this message]
2024-03-08 19:11 ` Linus Arver
2024-03-01 10:54 ` Karthik Nayak
2024-03-01 16:21 ` 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=xmqqsf1a7wse.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=linusa@google.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.
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).