From: Junio C Hamano <gitster@pobox.com>
To: Linus Arver <linusa@google.com>
Cc: Patrick Steinhardt <ps@pks.im>,
Linus Arver via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] RFC: add MAINTAINERS file
Date: Sat, 30 Mar 2024 14:44:03 -0700 [thread overview]
Message-ID: <xmqq5xx3l7j0.fsf@gitster.g> (raw)
In-Reply-To: <owlyr0fr61hy.fsf@fine.c.googlers.com> (Linus Arver's message of "Sat, 30 Mar 2024 11:03:21 -0700")
Linus Arver <linusa@google.com> writes:
> Patrick Steinhardt <ps@pks.im> writes:
>
>> On Sun, Mar 24, 2024 at 07:51:03PM -0700, Junio C Hamano wrote:
>>> Junio C Hamano <gitster@pobox.com> writes:
>> [...]
>>
>> I would thus reformulate the proposal from "MAINTAINERS" to "REVIEWERS".
>> Instead of saying that person A is a maintainer of subsystem B, it would
>> say person A has a keen interest in subsystem B and would thus be a very
>> good candidate to Cc in all your mails touching this subsystem.
>
> Good idea!
Seconded.
next prev parent reply other threads:[~2024-03-30 21:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 3:27 [PATCH] RFC: add MAINTAINERS file Linus Arver via GitGitGadget
2024-03-23 19:19 ` Junio C Hamano
2024-03-25 2:51 ` Junio C Hamano
2024-03-27 5:33 ` Linus Arver
2024-03-27 7:17 ` Patrick Steinhardt
2024-03-30 18:03 ` Linus Arver
2024-03-30 21:44 ` Junio C Hamano [this message]
2024-04-01 21:33 ` Taylor Blau
2024-04-01 22:13 ` Junio C Hamano
2024-04-02 0:22 ` Linus Arver
2024-04-02 5:39 ` Patrick Steinhardt
2024-04-02 5:46 ` Eric Sunshine
2024-04-02 5:59 ` Patrick Steinhardt
2024-03-26 22:24 ` Linus Arver
2024-03-26 23:39 ` Taylor Blau
2024-03-27 0:05 ` Junio C Hamano
2024-03-27 4:32 ` Linus Arver
2024-03-27 13:29 ` Junio C Hamano
2024-03-30 17:59 ` Linus Arver
2024-04-02 6:22 ` Patrick Steinhardt
2024-04-04 0:47 ` Linus Arver
2024-04-02 7:00 ` Patrick Steinhardt
2024-04-02 17:00 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5xx3l7j0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=linusa@google.com \
--cc=ps@pks.im \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).