From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 72891@debbugs.gnu.org, Florian Pelz <pelzflorian@pelzflorian.de>
Subject: [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams.
Date: Tue, 10 Sep 2024 09:21:58 +0900 [thread overview]
Message-ID: <87tteo73yx.fsf@gmail.com> (raw)
In-Reply-To: <fb9721adfc71b841dcb6a2575539449ce756e401.1725012038.git.ludo@gnu.org> ("Ludovic Courtès"'s message of "Fri, 30 Aug 2024 12:12:04 +0200")
Hello!
Ludovic Courtès <ludo@gnu.org> writes:
> * doc/contributing.texi (Teams): Define the purpose of teams; provide
> example; clarify membership and team creation.
> (Reviewing the Work of Others): Link to “Teams”.
>
> Change-Id: I5d75f69bc4653eb9da9c1d1f920718238ea83b9d
Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail>
Thanks for authoring it. I think the first two v2 patches of moving
things around by Simon would make sense as a follow-up, although I
haven't verified the result.
--
Maxim
next prev parent reply other threads:[~2024-09-10 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:12 [bug#72891] [PATCH RFC] doc: Define the purpose, membership, and creation of teams Ludovic Courtès
2024-08-31 6:26 ` Noé Lopez
2024-08-31 19:44 ` Ludovic Courtès
2024-09-04 17:26 ` Simon Tournier
2024-09-09 8:58 ` Ludovic Courtès
2024-09-09 17:48 ` Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 1/3] doc: contributing: Move consensus Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 2/3] doc: contributing: Move up section Teams Simon Tournier
2024-09-04 18:05 ` [bug#72891] [PATCH v2 3/3] doc: Define the purpose, membership, and creation of teams Simon Tournier
2024-09-05 9:16 ` pelzflorian (Florian Pelz)
2024-09-10 0:20 ` Maxim Cournoyer
2024-09-10 0:21 ` Maxim Cournoyer [this message]
2024-10-14 12:14 ` bug#72891: [PATCH RFC] " Ludovic Courtès
2024-10-14 17:37 ` [bug#72891] " Ludovic Courtès
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: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tteo73yx.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=72891@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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://git.savannah.gnu.org/cgit/guix.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).