From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: v2.46.1? was Re: What's cooking in git.git (Aug 2024, #06; Fri, 16)
Date: Tue, 20 Aug 2024 13:41:30 -0700 [thread overview]
Message-ID: <xmqqy14r53lx.fsf@gitster.g> (raw)
In-Reply-To: <7fcc8d92-d60b-2249-233d-7ce99ba96565@gmx.de> (Johannes Schindelin's message of "Tue, 20 Aug 2024 22:15:15 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> There is no immediate need for it and 2.46.1 does not even have to
>> happen. Just a grab bag of topics that are safe and are already on
>> track for 2.47 are kept in case we accumulate enough of them.
>
> Thank you for the clarification. I am a fan of getting things into the
> `maint` branch early, so I like what I am reading here.
Merging early, often, and in small batches will in theory make the
process safer by giving us more chance to see things unexpectedly
break, and that is why I too prefer it, but that is only true if
enough people are paying attention to the branch. I however have a
feeling that nobody uses 'maint' UNTIL the tip of it is tagged,
though..
prev parent reply other threads:[~2024-08-20 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 18:42 What's cooking in git.git (Aug 2024, #06; Fri, 16) Junio C Hamano
2024-08-19 16:49 ` v2.46.1? was " Johannes Schindelin
2024-08-19 19:16 ` Junio C Hamano
2024-08-20 20:15 ` Johannes Schindelin
2024-08-20 20:41 ` Junio C Hamano [this message]
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=xmqqy14r53lx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).