From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Patrick Steinhardt <ps@pks.im>,
Linus Arver via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Linus Arver <linusa@google.com>
Subject: Re: [PATCH] RFC: add MAINTAINERS file
Date: Mon, 01 Apr 2024 15:13:27 -0700 [thread overview]
Message-ID: <xmqqzfuc7muw.fsf@gitster.g> (raw)
In-Reply-To: <ZgsoOnle3CC8DqUR@nand.local> (Taylor Blau's message of "Mon, 1 Apr 2024 17:33:46 -0400")
Taylor Blau <me@ttaylorr.com> writes:
>> I don't think of this as "big enough to require this". I rather think
>> about the onboarding experience for new folks here. Sure, we can ask
>> them to "Please run git-shortlog(1) to figure out whom to Cc". But if we
>> instead provide a nice script that does it for them then we make their
>> lifes easier.
>
> Do you think that the script in contrib/contacts does a sufficient job
> at this?
Yup, that was my first reaction. If it is not sufficient to
mechanically mine history with shortlog or blame or contacts, and if
we can add a high quality hand-curated input to improve the result
contacts gives us, that would be a progress. I view the MAINTAINERS
format just one way to give such human generated input.
> Perhaps we haven't been as good at advertising this script as we could
> be, and that's why it isn't as widely used as it could be? I'm not sure.
Good point. Do we even mention it in MyFirstSomething docs?
next prev parent reply other threads:[~2024-04-01 22:13 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
2024-04-01 21:33 ` Taylor Blau
2024-04-01 22:13 ` Junio C Hamano [this message]
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=xmqqzfuc7muw.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=linusa@google.com \
--cc=me@ttaylorr.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).