git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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: Thu, 29 Feb 2024 18:02:17 -0800	[thread overview]
Message-ID: <xmqq1q8ubtg6.fsf@gitster.g> (raw)
In-Reply-To: <owlyil264yew.fsf@fine.c.googlers.com> (Linus Arver's message of "Thu, 29 Feb 2024 15:56:55 -0800")

Linus Arver <linusa@google.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> [...]
>> 
>> * la/trailer-api (2024-02-16) 9 commits
>>   (merged to 'next' on 2024-02-21 at 631e28bbbc)
>>  + format_trailers_from_commit(): indirectly call trailer_info_get()
>> ...
>>  Will merge to 'master'.
>>  source: <pull.1632.v5.git.1708124950.gitgitgadget@gmail.com>
>
> 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.

Thanks.


  reply	other threads:[~2024-03-01  2:02 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 [this message]
2024-03-01 16:16     ` Junio C Hamano
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

  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=xmqq1q8ubtg6.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.
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).