Re: What's cooking in git.git (Feb 2024, #09; Tue, 27)

From: Linus Arver <linusa@google.com>
Date: Mar 8, 2024, 19:11 UTC
Message-ID: <owlycys44jyu.fsf@fine.c.googlers.com>
In-Reply-To: <xmqqsf1a7wse.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 8 quoted lines

> 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,

Doh, I didn't realize this when I posted my message in this thread.

>> that's totally
>> unacceptable.

Completely understandable. In the future I will check "how long has the topic been in 'next'?" before asking to replace it with a newer revision.

Show 8 quoted lines

>> 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.

Ah I see --- thanks for stating for the record (and not leaving any room for me to get confused). Much appreciated.