From: Andreas Enge <andreas@enge.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, 63459@debbugs.gnu.org
Subject: [bug#63459] Changes to the branching/commit policy
Date: Fri, 9 Jun 2023 12:10:01 +0200 [thread overview]
Message-ID: <ZIL6eT8FN571kFVu@jurong> (raw)
In-Reply-To: <87y1kuyqew.fsf@cbaines.net>
Hello Chris,
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.
Looking forward to the merge since it clarifies things and removes the
staging and core-updates branches not only from our minds, but also the
texts.
Andreas
next parent reply other threads:[~2023-06-09 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y1kuyqew.fsf@cbaines.net>
2023-06-09 10:10 ` Andreas Enge [this message]
[not found] ` <87mt16xra3.fsf@cbaines.net>
2023-06-12 1:28 ` [bug#63459] Changes to the branching/commit policy Maxim Cournoyer
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=ZIL6eT8FN571kFVu@jurong \
--to=andreas@enge.fr \
--cc=63459@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).