From: Linus Arver <linusa@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2024, #09; Tue, 27)
Date: Fri, 08 Mar 2024 11:11:37 -0800 [thread overview]
Message-ID: <owlycys44jyu.fsf@fine.c.googlers.com> (raw)
In-Reply-To: <xmqqsf1a7wse.fsf@gitster.g>
Junio C Hamano <gitster@pobox.com> writes:
> 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.
>> 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.
next prev parent reply other threads:[~2024-03-08 19:11 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
2024-03-08 19:11 ` Linus Arver [this message]
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
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=owlycys44jyu.fsf@fine.c.googlers.com \
--to=linusa@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).