From: Christopher Baines <mail@cbaines.net>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, 63459@debbugs.gnu.org
Subject: Re: Changes to the branching/commit policy
Date: Sun, 11 Jun 2023 10:37:14 +0100 [thread overview]
Message-ID: <87mt16xra3.fsf@cbaines.net> (raw)
In-Reply-To: <ZIL6eT8FN571kFVu@jurong>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Andreas Enge <andreas@enge.fr> writes:
> thanks for taking up this issue! I agreed with Ludovic's comments, so
> things look good now for me. A very minor point: In the section on
> "trivial" changes, I would drop this sentence (which was already there
> before):
> "This is subject to being adjusted, allowing individuals to commit directly
> on non-controversial changes on parts they’re familiar with."
> The sentence is meaningless, as everything is all the time subject to being
> adjusted; and we do not have immediate plans to adjust it.
My reading of this line is that "adjusted" is probably not the right
word to use, but I think the intent here is to talk about how currently
it's accepted that people can and will push non-controversial changes on
parts they’re familiar with directly to master.
I'm not sure if others read this similarly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-06-11 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 14:24 Changes to the branching/commit policy Christopher Baines
2023-06-09 10:10 ` [bug#63459] " Andreas Enge
2023-06-11 9:37 ` Christopher Baines [this message]
2023-06-11 9:53 ` Andreas Enge
2023-06-12 1:28 ` [bug#63459] " Maxim Cournoyer
2023-06-12 20:23 ` Christopher Baines
2023-06-17 5:22 ` John Kehayias
2023-06-17 9:57 ` Christopher Baines
2023-06-19 18:39 ` John Kehayias
2023-06-20 3:52 ` Christopher Baines
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=87mt16xra3.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63459@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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).