All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: shejialuo <shejialuo@gmail.com>,
	 git@vger.kernel.org,  Karthik Nayak <karthik.188@gmail.com>
Subject: Re: What's cooking in git.git (Feb 2025, #09; Fri, 28)
Date: Tue, 04 Mar 2025 07:30:40 -0800	[thread overview]
Message-ID: <xmqqbjugu82n.fsf@gitster.g> (raw)
In-Reply-To: <Z8adWTssWtaNTfx4@pks.im> (Patrick Steinhardt's message of "Tue, 4 Mar 2025 07:27:37 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> So while I think that executing the command in git-fsck(1) is a good
> thing overall, I would feel a bit more comfortable if that last commit
> of the series landed in the next release cycle. But maybe I'm just being
> overly cautious?

Anything not in 'next' by -rc1 needs strong justification to further
advance during the cycle, so by default it would stay and cook in
'next' before the release.  I have a handful of topics in mind that
I do want to see merged before -rc2 but this was not one of them.

Thanks.

  parent reply	other threads:[~2025-03-04 15:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-01  0:45 What's cooking in git.git (Feb 2025, #09; Fri, 28) Junio C Hamano
2025-03-03 15:24 ` shejialuo
2025-03-03 17:03   ` Junio C Hamano
2025-03-04  6:27     ` Patrick Steinhardt
2025-03-04 12:25       ` shejialuo
2025-03-04 15:30       ` Junio C Hamano [this message]
2025-03-07 10:48     ` Karthik Nayak
2025-03-04  6:31 ` Patrick Steinhardt
2025-03-04  7:02   ` ps/reftable-sans-compat-util, was " Johannes Schindelin
2025-03-04  7:40     ` Johannes Schindelin
2025-03-04  9:46       ` Patrick Steinhardt
2025-03-04 10:06         ` Patrick Steinhardt
2025-03-26 16:57           ` Johannes Schindelin
2025-03-27 15:28             ` Junio C Hamano
2025-03-28  5:36               ` Patrick Steinhardt
2025-03-28 15:31                 ` Johannes Schindelin
2025-03-30  0:56                   ` Junio C Hamano
2025-03-29 23:56                 ` Junio C Hamano

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=xmqqbjugu82n.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.com \
    --cc=ps@pks.im \
    --cc=shejialuo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.