From: "Clément Lassieur" <clement@lassieur.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Suhail <suhail@bayesians.ca>, Steve George <steve@futurile.net>,
Edouard Klein <edou@rdklein.fr>,
guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: Guix Days: Patch flow discussion
Date: Fri, 16 Feb 2024 12:28:50 +0100 [thread overview]
Message-ID: <87plwwlkb1.fsf@lassieur.org> (raw)
In-Reply-To: <Zc9A5SPGsK1E-ZJW@jurong> (Andreas Enge's message of "Fri, 16 Feb 2024 12:03:01 +0100")
On Fri, Feb 16 2024, Andreas Enge wrote:
> Am Fri, Feb 16, 2024 at 11:56:50AM +0100 schrieb Clément Lassieur:
>> Would it makes sense to have a "does-not-apply" tag too?
>
> Should this not appear in the QA page, assuming that once all the new
> issues are closed, older ones will bubble to the top and be treated by QA?
> (I am not sure if just looking at the n latests issues is how QA works,
> but I think so.)
I think it would be useful (at least for me) if I browse a list of
patches that I want to review, to document why a review can't be done.
Also, so that other people won't try to apply it.
It would be great that QA does that job, I imagine when it does it it
can also add that tag.
next prev parent reply other threads:[~2024-02-16 11:30 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35786.5440238797$1707248619@news.gmane.org>
2024-02-16 10:56 ` Guix Days: Patch flow discussion Clément Lassieur
2024-02-16 11:03 ` Andreas Enge
2024-02-16 11:28 ` Clément Lassieur [this message]
2024-02-16 12:06 ` Christopher Baines
2024-02-18 2:31 Suhail
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 21:01 Suhail
2024-02-06 20:00 Suhail
2024-02-07 13:41 ` Josselin Poiret
2024-02-07 13:46 ` Josselin Poiret
2024-02-11 17:24 ` Vagrant Cascadian
2024-02-22 5:42 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-11 20:04 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-11 20:21 ` Clément Lassieur
2024-02-11 20:39 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-11 22:08 ` Clément Lassieur
2024-02-12 10:35 ` Josselin Poiret
2024-02-12 11:19 ` Clément Lassieur
2024-02-12 15:57 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-13 9:31 ` Josselin Poiret
2024-02-13 14:30 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-14 9:21 ` Josselin Poiret
2024-02-07 14:30 ` Clément Lassieur
2024-02-07 20:18 ` Ricardo Wurmus
2024-02-08 2:39 ` Kyle Meyer
2024-02-11 16:38 ` Maxim Cournoyer
2024-02-14 15:48 ` Simon Tournier
2024-02-15 11:07 ` Josselin Poiret
2024-02-15 12:45 ` Simon Tournier
2024-02-15 11:45 ` Clément Lassieur
2024-02-15 11:51 ` Clément Lassieur
2024-02-15 15:32 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-15 17:19 ` Simon Tournier
2024-02-16 14:27 ` Maxim Cournoyer
2024-02-15 13:06 ` Simon Tournier
2024-02-15 17:24 ` Clément Lassieur
2024-02-15 18:40 ` Simon Tournier
2024-02-15 22:08 ` Clément Lassieur
2024-03-01 22:04 ` Attila Lendvai
2024-02-16 14:25 ` Maxim Cournoyer
2024-02-06 19:47 Suhail
2024-02-06 19:42 Suhail
2024-02-05 21:45 Suhail
[not found] <65c12e7e.0c0a0220.d7729.823cSMTPIN_ADDED_BROKEN@mx.google.com>
2024-02-05 19:52 ` Felix Lechner via
2024-02-05 19:33 Andy Tai
2024-02-05 20:50 ` Clément Lassieur
2024-02-06 7:58 ` Andy Tai
2024-02-05 18:51 Suhail
2024-02-06 16:51 ` Steve George
2024-02-05 18:44 Suhail
2024-02-05 19:59 ` Hartmut Goebel
2024-02-06 11:14 ` Josselin Poiret
[not found] <34679.2393991322$1707153777@news.gmane.org>
2024-02-05 17:36 ` Clément Lassieur
2024-02-05 17:21 Suhail
2024-02-05 17:25 ` Vivien Kraus
2024-02-06 11:27 ` Josselin Poiret
2024-02-05 9:39 Steve George
2024-02-05 14:07 ` Leo Famulari
2024-02-05 15:00 ` Tomas Volf
2024-02-05 22:08 ` Wilko Meyer
2024-02-06 11:49 ` Tomas Volf
2024-02-06 12:09 ` Clément Lassieur
2024-02-06 12:53 ` Tomas Volf
2024-02-05 21:57 ` Steve George
2024-02-05 15:57 ` Clément Lassieur
2024-02-05 17:10 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-02-05 17:28 ` Clément Lassieur
2024-02-05 18:27 ` Felix Lechner via
2024-02-05 18:50 ` Clément Lassieur
2024-02-05 22:10 ` Steve George
2024-02-05 18:07 ` Hartmut Goebel
2024-02-05 22:29 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:31 ` Steve George
2024-02-05 22:32 ` Steve George
2024-02-05 22:32 ` Steve George
2024-02-05 22:33 ` Steve George
2024-02-05 22:50 ` Steve George
2024-02-06 13:27 ` Edouard Klein
2024-02-06 13:39 ` Steve George
2024-02-08 19:56 ` Skyler Ferris
2024-02-09 16:35 ` Edouard Klein
2024-02-09 16:46 ` Andreas Enge
2024-02-11 10:03 ` Steve George
2024-02-14 21:40 ` Simon Tournier
2024-02-28 17:51 ` Giovanni Biscuolo
2024-02-28 19:21 ` Matt
2024-02-29 15:41 ` Daniel Littlewood
2024-02-29 18:09 ` Andreas Enge
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=87plwwlkb1.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=andreas@enge.fr \
--cc=edou@rdklein.fr \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=steve@futurile.net \
--cc=suhail@bayesians.ca \
/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).