From: Christopher Baines <mail@cbaines.net>
To: 59513-done@debbugs.gnu.org
Subject: bug#59513: [PATCH v2] doc: contributing: Tweak the Commit Policy.
Date: Wed, 11 Jan 2023 10:50:22 +0000 [thread overview]
Message-ID: <871qo1fioh.fsf@cbaines.net> (raw)
In-Reply-To: <20221208112051.5019-1-mail@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Add more examples of when it can be appropriate to push changes without
> review, as I think this can be appropriate in the case of trivial changes (as
> mentioned before), but also non-trivial fixes.
>
> No longer suggest pushing simple new packages or package upgrades (that don't
> cause lots of rebuilds) without sending to guix-patches. Now there's some
> automation for testing changes sent to guix-patches, sending changes there
> before pushing can mean that more rigerious testing takes place and help speed
> up substitutes becoming available. This is true, even if no human review takes
> place.
>
> Only suggest waiting one week for review for simpler changes, wait two weeks
> for more significant changes.
>
> Also, reorder some of the information in this section so it's grouped together
> better.
>
> * doc/contributing.texi (Commit Policy): Tweak.
> ---
> doc/contributing.texi | 41 ++++++++++++++++++-----------------------
> 1 file changed, 18 insertions(+), 23 deletions(-)
I've now pushed this to master as
9aa2b7419854306b7ae78d4c4f7684316b834b1d, with some final tweaks.
Thanks everyone for taking a look.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2023-01-11 10:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 10:49 [bug#59513] [PATCH] doc: contributing: Tweak the Commit Policy Christopher Baines
2022-11-23 20:27 ` zimoun
2022-11-24 8:40 ` Christopher Baines
2022-11-24 11:59 ` zimoun
2022-11-28 11:46 ` Christopher Baines
2022-12-02 9:45 ` Ludovic Courtès
2022-12-01 21:44 ` Ludovic Courtès
2022-12-12 10:33 ` Christopher Baines
2022-12-12 11:47 ` Ludovic Courtès
2022-12-08 11:20 ` [bug#59513] [PATCH v2] " Christopher Baines
2022-12-08 13:53 ` Liliana Marie Prikler
2022-12-12 10:49 ` Christopher Baines
2022-12-12 20:27 ` Liliana Marie Prikler
2022-12-13 14:06 ` Christopher Baines
2022-12-14 0:54 ` Vagrant Cascadian
2022-12-14 10:21 ` Christopher Baines
2022-12-20 10:55 ` Ludovic Courtès
2022-12-17 5:01 ` [bug#59513] [PATCH] " Maxim Cournoyer
2023-01-05 9:12 ` [bug#59513] [PATCH v2] " zimoun
2023-01-11 10:48 ` Christopher Baines
2023-01-11 10:50 ` Christopher Baines [this message]
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=871qo1fioh.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=59513-done@debbugs.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 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).