From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC] How to accellerate the patch flow (or should we?)
Date: Mon, 29 Sep 2025 15:12:52 -0700 [thread overview]
Message-ID: <xmqq4isk7vrv.fsf@gitster.g> (raw)
In-Reply-To: <87792693-58d9-4047-beae-38aa4c59ed41@app.fastmail.com> (Kristoffer Haugsbakk's message of "Mon, 29 Sep 2025 22:04:49 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
>> The time taken during 7. is pretty much fixed and unless we are
>> willing to sacrifice the quality of the end result, cannot
>> reasonably be shortened (note that this is based on the assumption
>> that "find any remaining bugs while it is in 'next' before it hits
>> 'master'" philosophy is working, but we have never run experiments
>> to shorten this to say 3 days to see if we see more bugs on 'master'
>> yet).
>
> Maybe pure documentation changes could cook for less than seven days.
Yup, that kind of adjustment at the maintainer's discretion has
already been applied, depending on the nature of a topic. Some
truly trivial typofixes may not even go through 'next' but get
applied to 'master' directly.
Thanks.
prev parent reply other threads:[~2025-09-29 22:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 22:24 [RFC] How to accellerate the patch flow (or should we?) Junio C Hamano
2025-09-27 21:32 ` Taylor Blau
2025-09-28 0:19 ` Junio C Hamano
2025-09-28 2:21 ` Taylor Blau
2025-09-29 22:23 ` Patrick Steinhardt
2025-09-29 22:46 ` Junio C Hamano
2025-09-29 23:25 ` Patrick Steinhardt
2025-10-01 20:00 ` Junio C Hamano
2025-09-30 20:02 ` Taylor Blau
2025-09-30 20:28 ` Junio C Hamano
2025-09-29 20:12 ` Kristoffer Haugsbakk
2025-09-29 21:19 ` Ben Knoble
2025-09-29 22:23 ` Patrick Steinhardt
2025-09-29 22:23 ` Patrick Steinhardt
2025-09-30 20:04 ` Taylor Blau
2025-09-29 20:04 ` Kristoffer Haugsbakk
2025-09-29 22:12 ` 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=xmqq4isk7vrv.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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).