Re: What's cooking in git.git (Sep 2026, #03)

[Junio C Hamano <gitster@pobox.com>]

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> On Tue, Sep 8, 2026, at 10:37, Junio C Hamano wrote:
>> Here are the topics that have been cooking in my tree.  Commits
>> prefixed with '+' are in 'next' (being in 'next' is a sign that a
>> topic is stable enough to be used and is a candidate to be in a
>> future release).  Commits prefixed with '-' are only in 'seen', and
>> aren't considered "accepted" at all.  They may be annotated with a URL
>> to a message that raises issues but they are by no means exhaustive.
>> A topic without enough support may be discarded after a long period
>> of no activity (of course, it can be resubmitted when new interest
>> arises).
>>
>>[snip]
>
> There’s also a topic from Sep 7th that I don’t see listed here, for your
> information.
>
> <20260907-maintenance-doc-bullet-fix-v1-1-dc08dbe61a82@brighamcampbell.com>

It is very likely that anything missing was simply overlooked (It
also is possible that it wasn't interesting).  It is far easier to
pick up if you resend it, rather than sending an message-ID of it.

Doing so also shows that somebody other than the original author
cares enough to do so (especially if the re-sender adds their own
acked-by).

I think I did not touch it back then because the discussion
identified needs for further work, and decided to leave it up to the
author, i.e., if the author cares enough, a final reroll will come,
at which point I may pick it up, otherwise I can safely ignore such
a patch even whose author does not care enough.

Thanks for pinging.