From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2025, #06; Tue, 20)
Date: Wed, 21 May 2025 07:55:37 -0700 [thread overview]
Message-ID: <xmqqtt5ec8t2.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZR-OaLPueyRcXYrN0rKPnVXPPmJ6drsmM4eRs-6yKEgQQ@mail.gmail.com> (Karthik Nayak's message of "Wed, 21 May 2025 05:10:24 -0500")
Karthik Nayak <karthik.188@gmail.com> writes:
>> Will merge to 'next'?
>> source: <20250519-501-update-git-fetch-1-to-use-partial-transactions-v3-0-6cdfd4f769b9@gmail.com>
>
> Incase you missed the cover letter: I would say that while this can be
> merged to 'next', we should delay the merge to 'master' for after the
> 2.50 release since it can be disruptive. Mostly letting it bake for a
> longer time before hitting a major release.
What are the things you are so unsure about and guinea pigs who use
'next' as their daily driver should watch out for?
next prev parent reply other threads:[~2025-05-21 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 0:54 What's cooking in git.git (May 2025, #06; Tue, 20) Junio C Hamano
2025-05-21 10:10 ` Karthik Nayak
2025-05-21 14:55 ` Junio C Hamano [this message]
2025-05-22 8:57 ` Karthik Nayak
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=xmqqtt5ec8t2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@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 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).