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

Re: What's cooking in git.git (Nov 2022, #07; Tue, 29)

From
Taylor Blau <me@ttaylorr.com>
Date
Nov 29, 2022, 18:00 UTC
Message-ID
<Y4ZI21F0yYxMk3O3@nand.local>
In-Reply-To
<20221129130841.82302-1-tenglong.tl@alibaba-inc.com>
On Tue, Nov 29, 2022 at 09:08:41PM +0800, Teng Long wrote:
Show 8 quoted lines
>
> > * tl/pack-bitmap-absolute-paths (2022-11-29) 4 commits
> >  - pack-bitmap.c: trace bitmap ignore logs when midx-bitmap is found
> >  - pack-bitmap.c: break out of the bitmap loop early if not tracing
> >   (merged to 'next' on 2022-11-14 at 34eb0ea05a)
>
> Will the two commits which merged to 'next' on 2022-11-14 at 34eb0ea05a
> be taken into 2.39.0-rc0 (or v2.39.0 is frozen already)?

It is rather late in the release cycle to include new patches. I wouldn't be sad to see them in, either, since they are pretty low risk in my opinion.

But I think a safe assumption to make is that they *won't* be in 2.39.0, and that you should resubmit all four as a new series once 'next' is rewound.

Thanks, Taylor

Previous: Teng LongNext: Teng Long
Message 3 of 7 in “[ANNOUNCE] Git v2.39.0-rc0”
  1. Junio C HamanoNov 23, 2022
  2. What's cooking in git.git (Nov 2022, #07; Tue, 29)Teng Long, Nov 29, 2022
  3. Taylor BlauNov 29, 2022
  4. Teng LongNov 30, 2022
  5. Junio C HamanoNov 30, 2022
  6. Teng LongNov 30, 2022
  7. Taylor BlauNov 30, 2022

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.