From: Junio C Hamano <gitster@pobox.com>
To: Michael Montalbo <mmontalbo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] SubmittingPatches: abandoning a series
Date: Tue, 07 Jul 2026 21:52:14 -0700 [thread overview]
Message-ID: <xmqqechew0ap.fsf@gitster.g> (raw)
In-Reply-To: <CAC2QwmJ8Z7hZHk9SofRsprvAR3B=UXUkeyy7i4uofRi-xEymow@mail.gmail.com> (Michael Montalbo's message of "Tue, 7 Jul 2026 20:31:24 -0700")
Michael Montalbo <mmontalbo@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>> + A discussion on the list might convince you that your changes are
>> + not such a good idea, in which case you are expected to explicitly
>> + retract the topic, to releave the maintainer from having to worry
>> + about it.
...
Thanks for improvements.
> Finally, maybe a rule of thumb as to how old a topic a topic should get
> before a "staleness" update is provided would be helpful, or maybe that
> is too contextually dependent / would potentially introduce some
> unwanted scheduling contract?
>
> Overall, I think the explicit guidance is helpful.
I've been working on streamlining my workflow to manage the "What's
cooking" report, and writing down guidelines with concrete numbers.
* When the discussion seems to reach rough consensus that the
latest round looks good for 'next', the topic is immediately
marked as "Will merge to 'next'?" in my draft copy (note: I do
not want to spam the list with "What's cooking" too often, but it
is the document I work from, and it is updated multiple times a
day).
* After no negative opinions are seen on a topic in "Will merge to
'next'?" state for about 36 hours, the topic is marked as "Will
merge to 'next'". I will merge such topics during the next
integration cycle (note: I can only have up to two integration
cycles per day due to time constraints).
* Imagine that a topic was last updated more than 4 weeks ago. If
there are review comments on the topic that are left unanswered
by the author for more than a week, and if nothing happens in the
discussion thread other than inquiry on the current status, the
topic is marked as "stalled". I will try to notice and ping a
stalled topic once or twice, but after that I may discard such a
topic (which by the way I really hate having to decide to do so).
* After a topic is merged to 'next', if nothing negative that needs
fixing is discovered for 7 calendar days, the topic is merged to
'master'. I may shorten this depending on how complex the topic
is.
THere may be more, but these are what I can think of offhand.
next prev parent reply other threads:[~2026-07-08 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 3:31 [PATCH] SubmittingPatches: abandoning a series Michael Montalbo
2026-07-08 4:52 ` Junio C Hamano [this message]
2026-07-08 5:43 ` Weijie Yuan
2026-07-08 16:33 ` Junio C Hamano
2026-07-08 5:27 ` Weijie Yuan
2026-07-08 5:41 ` Michael Montalbo
2026-07-08 6:21 ` Weijie Yuan
-- strict thread matches above, loose matches on Subject: below --
2026-07-08 1:20 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=xmqqechew0ap.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mmontalbo@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