From: Junio C Hamano <gitster@pobox.com>
To: Derrick Stolee <stolee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: ds/revision-maximal-only (was Re: What's cooking in git.git (Feb 2026, #05))
Date: Tue, 17 Feb 2026 08:33:14 -0800 [thread overview]
Message-ID: <xmqqzf57cotx.fsf@gitster.g> (raw)
In-Reply-To: <966fe2a3-1565-4bc6-ab4e-433fd4ff517f@gmail.com> (Derrick Stolee's message of "Sat, 14 Feb 2026 16:17:36 -0500")
Derrick Stolee <stolee@gmail.com> writes:
> On 2/13/26 9:01 PM, Junio C Hamano wrote:
>
>> * ds/revision-maximal-only (2026-01-22) 1 commit
>> - revision: add --maximal-only option
>>
>> "git rev-list" and friends learn "--maximal-only" to show only the
>> commits that are not reachable by other commits.
>>
>> Will merge to 'next'?
>> source: <pull.2032.v2.git.1769097958549.gitgitgadget@gmail.com>
>
> This has been stable for a few weeks, so I think it's ready for
> 'next'.
I am not 100% sure if "stable" is the most appropriate word to
describe the topic, or if it is "dormant". Let's merge it down.
Thanks.
next prev parent reply other threads:[~2026-02-17 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 2:01 What's cooking in git.git (Feb 2026, #05) Junio C Hamano
2026-02-14 21:17 ` ds/revision-maximal-only (was Re: What's cooking in git.git (Feb 2026, #05)) Derrick Stolee
2026-02-17 16:33 ` Junio C Hamano [this message]
2026-02-16 6:56 ` What's cooking in git.git (Feb 2026, #05) Patrick Steinhardt
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=xmqqzf57cotx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=stolee@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