From: Teng Long <dyroneteng@gmail.com>
To: me@ttaylorr.com
Cc: dyroneteng@gmail.com, git-packagers@googlegroups.com,
git@vger.kernel.org, gitster@pobox.com, lwn@lwn.net
Subject: Re: What's cooking in git.git (Nov 2022, #07; Tue, 29)
Date: Wed, 30 Nov 2022 20:41:21 +0800 [thread overview]
Message-ID: <20221130124121.97048-1-dyroneteng@gmail.com> (raw)
In-Reply-To: <Y4ZI21F0yYxMk3O3@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
> > 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, it's unnecessary to hitchhiking after I read the reply of Junio.
next prev parent reply other threads:[~2022-11-30 12:41 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 [this message]
2022-11-30 3:53 ` Junio C Hamano
2022-11-30 12:34 ` Teng Long
2022-11-30 16:42 ` Taylor Blau
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221130124121.97048-1-dyroneteng@gmail.com \
--to=dyroneteng@gmail.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lwn@lwn.net \
--cc=me@ttaylorr.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).