From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: "Ricardo Wurmus" <rekado@elephly.net>,
"Josselin Poiret" <dev@jpoiret.xyz>,
"Christopher Baines" <mail@cbaines.net>,
"Simon Tournier" <zimon.toutoune@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>,
"Tobias Geerinckx-Rice" <me@tobias.gr>,
60218@debbugs.gnu.org
Subject: [bug#60218] [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman)
Date: Tue, 27 Dec 2022 10:35:12 -0500 [thread overview]
Message-ID: <8735907tcf.fsf@gmail.com> (raw)
In-Reply-To: <87pmc5maj2.fsf_-_@gnu.org> (Mathieu Othacehe's message of "Tue, 27 Dec 2022 11:00:17 +0100")
Hi Mathieu,
Mathieu Othacehe <othacehe@gnu.org> writes:
> Hey Maxim,
>
>> cc <team-name> get git send-email flags for cc-ing <team-name>
>> cc-members <start> <end> cc teams related to files changed between revisions
>> list-teams list teams and their members
>> - list-members <team-name> list members belonging to <team-name>~%"))))
>> + list-members <team-name> list members belonging to <team-name>~%
>> + get-maintainer <patch> compatibility mode with Linux get_maintainer.pl"))))
>
> Maybe it could be interesting to also add this patch mode to the
> cc-members command, this way for instance:
>
> cc-members [<start> <end>|<patch> ...]
Implemented in v2! I guess it could be useful. Note that it doesn't
parse the patch for the file names touched, instead it assumes the patch
was produced from a commit registered in git and then use the usual code
path (for simplicity).
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-12-27 15:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 13:58 [bug#60218] [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman) Maxim Cournoyer
2022-12-20 14:13 ` [bug#60218] [PATCH 1/2] teams: Add a "get-maintainer" command Maxim Cournoyer
2022-12-20 14:13 ` [bug#60218] [PATCH 2/2] .patman: New configuration file Maxim Cournoyer
2022-12-24 23:15 ` [bug#60218] [PATCH 1/2] teams: Add a "get-maintainer" command Ricardo Wurmus
2022-12-27 3:19 ` Maxim Cournoyer
2022-12-27 10:00 ` [bug#60218] [PATCH 0/2] New teams.scm 'get-maintainer' command (for integration with patman) Mathieu Othacehe
2022-12-27 15:35 ` Maxim Cournoyer [this message]
2022-12-28 17:22 ` Mathieu Othacehe
2022-12-28 20:42 ` bug#60218: " Maxim Cournoyer
2022-12-27 15:32 ` [bug#60218] [PATCH v2 1/3] teams: Add a "get-maintainer" command Maxim Cournoyer
2022-12-27 15:32 ` [bug#60218] [PATCH v2 2/3] teams: Allow a patch-file argument to cc-members Maxim Cournoyer
2022-12-27 15:32 ` [bug#60218] [PATCH v2 3/3] .patman: New configuration file Maxim Cournoyer
2023-01-06 17:26 ` Simon Tournier
2023-01-11 15:10 ` zimoun
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=8735907tcf.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=60218@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.