From: Patrick Steinhardt <ps@pks.im>
To: Taylor Blau <me@ttaylorr.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [RFC] How to accellerate the patch flow (or should we?)
Date: Tue, 30 Sep 2025 00:23:44 +0200 [thread overview]
Message-ID: <aNsG8JGvpzui7XJA@pks.im> (raw)
In-Reply-To: <aNhX9AJ/zq4IYhmW@nand.local>
On Sat, Sep 27, 2025 at 05:32:36PM -0400, Taylor Blau wrote:
> That would leave topics which do not have active reviewers in a lurch,
> but I think that is sort of the point. Contributors should expect to do
> some of the work of making sure their topics get reviewed themselves,
> and that shouldn't fall entirely on the maintainer.
I guess this is a realistic expectation for oldtimers on the mailing
list. And it especially is a possibility for developers that work in a
team, as they can basically tell others to do a review. But newcomers
already have a hard time to contribute to Git, so we should make sure
that we don't put more of the burden on them.
Patrick
next prev parent reply other threads:[~2025-09-29 22:23 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 [this message]
2025-09-30 20:04 ` Taylor Blau
2025-09-29 20:04 ` Kristoffer Haugsbakk
2025-09-29 22:12 ` 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=aNsG8JGvpzui7XJA@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).