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