git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Nov 2024, #07; Wed, 20)

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Nov 21, 2024, 08:26 UTC
Message-ID
<a340dfc9-bc3a-40d2-a8ec-fc47c00d1305@app.fastmail.com>
In-Reply-To
<xmqqo72ai929.fsf@gitster.g>
Hi
On Wed, Nov 20, 2024, at 09:49, Junio C Hamano wrote:
Show 9 quoted lines
> * 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/
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 12 in “What's cooking in git.git (Nov 2024, #07; Wed, 20)”
  1. Junio C HamanoNov 20, 2024
  2. Patrick SteinhardtNov 20, 2024
  3. shejialuoNov 20, 2024
  4. Junio C HamanoNov 21, 2024
  5. karthik nayakNov 20, 2024
  6. Taylor BlauNov 20, 2024
  7. Junio C HamanoNov 21, 2024
  8. Junio C HamanoNov 22, 2024
  9. Kristoffer HaugsbakkNov 21, 2024
  10. Junio C HamanoNov 21, 2024
  11. Kristoffer HaugsbakkNov 21, 2024
  12. Junio C HamanoNov 21, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.