From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Teng Long <dyroneteng@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2022, #07; Tue, 29)
Date: Wed, 30 Nov 2022 11:42:58 -0500 [thread overview]
Message-ID: <Y4eIEscigSZ3vClo@nand.local> (raw)
In-Reply-To: <xmqqa64914jj.fsf@gitster.g>
[-cc git-packagers, lwn]
On Wed, Nov 30, 2022 at 12:53:36PM +0900, Junio C Hamano wrote:
> Teng Long <dyroneteng@gmail.com> writes:
>
> >> * 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)?
>
> 2.39-rc0 was a preview of topics that were already done at that
> point about a week ago. A topic that is not in -rc0 may hit the
> release, but it depends on how urgent the "fix" is, I would say.
> Unless there is a good reason not to, any topic should spend at
> least a week to cook in 'next' before graduating, and because there
> typically is about a week between -rc0 and -rc1, anything outside
> 'next' when -rc0 was tagged is not likely to have spent a week in
> 'next' when -rc1 is done.
>
> We could graduate the early bits separately, but is it so urgent a
> fix to get them in?
They are nice-to-have, but certainly not essential.
Thanks,
Taylor
next prev parent reply other threads:[~2022-11-30 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 7:25 [ANNOUNCE] Git v2.39.0-rc0 Junio C Hamano
2022-11-29 13:08 ` What's cooking in git.git (Nov 2022, #07; Tue, 29) Teng Long
2022-11-29 18:00 ` Taylor Blau
2022-11-30 12:41 ` Teng Long
2022-11-30 3:53 ` Junio C Hamano
2022-11-30 12:34 ` Teng Long
2022-11-30 16:42 ` Taylor Blau [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 9:40 Junio C Hamano
2022-11-29 19:08 ` Glen Choo
2022-11-30 3:45 ` Junio C Hamano
2022-11-30 18:08 ` Glen Choo
2022-11-30 10:02 ` Phillip Wood
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=Y4eIEscigSZ3vClo@nand.local \
--to=me@ttaylorr.com \
--cc=dyroneteng@gmail.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.
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).