From: Andreas Enge <andreas@enge.fr>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Proposed changes to the commit policy (#59513)
Date: Wed, 1 Feb 2023 14:09:13 +0100 [thread overview]
Message-ID: <Y9pkeZgfY3aMzsRX@jurong> (raw)
In-Reply-To: <877cx34q5k.fsf@cbaines.net>
Am Mon, Jan 30, 2023 at 10:03:14PM +0000 schrieb Christopher Baines:
> changes happen more slowly, but this is why I'm working on the tools and
> processes, as I think that's a path to trying to maintain and improve
> the quality while reducing the impact to pace and enjoyment.
> I'm sure there are ways of addressing at least some of the problems you
> mention above
One idea that came to my mind is that once the patch passes all tests
in automatic quality assurance, it could be committed automatically and
the bug closed (well, maybe not any patches, but at least these kind of
update patches, or specially tagged ones). This would not force people
to get back to them.
However I think it cannot work, since it means rebasing on the current
master, which invalidates the signature of the commit.
Andreas
next prev parent reply other threads:[~2023-02-01 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 14:10 Proposed changes to the commit policy (#59513) Christopher Baines
2023-01-16 21:47 ` Christopher Baines
2023-01-17 16:35 ` Ludovic Courtès
2023-01-18 11:23 ` Andreas Enge
2023-01-18 11:45 ` Christopher Baines
2023-01-18 16:54 ` Kaelyn
2023-01-22 17:18 ` Andreas Enge
2023-01-23 9:24 ` Simon Tournier
2023-01-24 9:07 ` Attila Lendvai
2023-01-25 15:03 ` Proposed changes to the commit policy Andreas Enge
2023-01-30 21:40 ` Ludovic Courtès
2023-02-13 11:41 ` Efraim Flashner
2023-01-30 22:03 ` Proposed changes to the commit policy (#59513) Christopher Baines
2023-01-31 11:00 ` Simon Tournier
2023-02-01 13:09 ` Andreas Enge [this message]
2023-01-20 11:50 ` Simon Tournier
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=Y9pkeZgfY3aMzsRX@jurong \
--to=andreas@enge.fr \
--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).