From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 48696@debbugs.gnu.org
Subject: [bug#48696] [PATCH 0/3] Documenting commit reverts and revocation
Date: Thu, 27 May 2021 10:16:28 -0400 [thread overview]
Message-ID: <YK+pvNseB4Oc05Qc@jasmine.lan> (raw)
In-Reply-To: <20210527123259.4115-1-ludo@gnu.org>
On Thu, May 27, 2021 at 02:32:59PM +0200, Ludovic Courtès wrote:
> Hello Guix!
>
> Attached is an attempt to:
>
> 1. Structure the “Commit Access” section of the manual;
>
> 2. Document how to address committers’ mistakes, when to revert
> commits;
>
> 3. Explain under what circumstances maintainers may revoke commit
> rights.
>
> It essentially codifies unwritten rules, but as always, I think it’s
> better to be explicit about the rules and community expectations.
>
> Let me know what you think! I propose to leave a comment period
> of at least one week, possibly iterating with new versions.
Thanks for putting this together. It looks good to me!
next prev parent reply other threads:[~2021-05-27 14:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 12:32 [bug#48696] [PATCH 0/3] Documenting commit reverts and revocation Ludovic Courtès
2021-05-27 12:35 ` [bug#48696] [PATCH 1/3] doc: Structure the "Commit Access" section Ludovic Courtès
2021-05-27 12:35 ` [bug#48696] [PATCH 2/3] doc: Add "Addressing Mistakes" section Ludovic Courtès
2021-05-27 19:19 ` Christopher Baines
2021-05-29 10:22 ` Ludovic Courtès
2021-05-30 10:29 ` Christopher Baines
2021-06-02 9:22 ` [bug#48696] [PATCH 0/3] Documenting commit reverts and revocation Ludovic Courtès
2021-06-08 14:02 ` Christopher Baines
2021-06-11 14:05 ` Ludovic Courtès
2021-06-13 10:15 ` [bug#48696] [PATCH v2 0/4] " Ludovic Courtès
2021-06-13 10:15 ` [bug#48696] [PATCH v2 1/4] doc: Structure the "Commit Access" section Ludovic Courtès
2021-06-13 11:50 ` Xinglu Chen
2021-06-13 11:56 ` Xinglu Chen
2021-06-13 10:15 ` [bug#48696] [PATCH v2 2/4] doc: Add "Addressing Issues" section Ludovic Courtès
2021-06-13 10:15 ` [bug#48696] [PATCH v2 3/4] doc: Explain more reasons for commit revocation Ludovic Courtès
2021-06-13 10:15 ` [bug#48696] [PATCH v2 4/4] doc: Clarify Git commit signing; fix typo Ludovic Courtès
2021-06-18 12:37 ` bug#48696: [PATCH 0/3] Documenting commit reverts and revocation Ludovic Courtès
2021-05-27 12:35 ` [bug#48696] [PATCH 3/3] doc: Explain more reasons for commit revocation Ludovic Courtès
2021-05-27 19:13 ` Maxime Devos
2021-05-27 20:07 ` Christopher Baines
2021-05-29 9:58 ` Ludovic Courtès
2021-05-29 11:28 ` Christopher Baines
2021-05-29 20:36 ` Ludovic Courtès
2021-05-27 13:55 ` [bug#48696] [PATCH 1/3] doc: Structure the "Commit Access" section Julien Lepiller
2021-05-29 9:30 ` Ludovic Courtès
2021-05-27 19:10 ` Maxime Devos
2021-05-27 14:16 ` Leo Famulari [this message]
2021-05-30 12:49 ` [bug#48696] [PATCH 0/3] Documenting commit reverts and revocation Tobias Geerinckx-Rice via Guix-patches via
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=YK+pvNseB4Oc05Qc@jasmine.lan \
--to=leo@famulari.name \
--cc=48696@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.