git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #07; Wed, 20)
Date: Thu, 21 Nov 2024 09:26:53 +0100	[thread overview]
Message-ID: <a340dfc9-bc3a-40d2-a8ec-fc47c00d1305@app.fastmail.com> (raw)
In-Reply-To: <xmqqo72ai929.fsf@gitster.g>

Hi

On Wed, Nov 20, 2024, at 09:49, Junio C Hamano wrote:
> * kh/trailer-in-glossary (2024-11-18) 1 commit
>   (merged to 'next' on 2024-11-20 at fad433e2f4)
>  + Documentation/glossary: describe "trailer"
>
>  Doc updates.
>
>  Will merge to 'master'.
>  source:
> <ba35ba3ec212860a3151cfad582a384a50c55e6a.1731871683.git.code@khaugsbakk.name>

I’m just asking for future topics here, not that this needs to be changed. This
topic went into `next` pretty fast. So I didn’t get around to sending a new
version with Christian’s Ack.[1] I just let it sit there for that week in case
there was any more input. What should be done about what one might call a
trailer topic version for simple topics that might get included in `next` soon
after being proposed?

Thanks

🔗 1: https://lore.kernel.org/git/CAP8UFD3p3ts_7kvk_Zm2efhcPUcEFnLcLFPAqzb40d46BTVzyA@mail.gmail.com/

  parent reply	other threads:[~2024-11-21  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  8:49 What's cooking in git.git (Nov 2024, #07; Wed, 20) Junio C Hamano
2024-11-20 10:36 ` Patrick Steinhardt
2024-11-20 13:41   ` shejialuo
2024-11-21  1:10   ` Junio C Hamano
2024-11-20 10:39 ` karthik nayak
2024-11-20 16:40 ` Taylor Blau
2024-11-21  0:44   ` Junio C Hamano
2024-11-22  4:34   ` Junio C Hamano
2024-11-21  8:26 ` Kristoffer Haugsbakk [this message]
2024-11-21 12:59   ` Junio C Hamano
2024-11-21 15:31     ` Kristoffer Haugsbakk
2024-11-21 23:11       ` 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=a340dfc9-bc3a-40d2-a8ec-fc47c00d1305@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.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. 
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).