From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Process for reviewing patches as someone without commit access
Date: Thu, 07 Sep 2023 11:55:57 +0200 [thread overview]
Message-ID: <87bkeemhn6.fsf@gmail.com> (raw)
In-Reply-To: <87jzt2og1z.fsf@gmail.com>
Hi,
On Wed, 06 Sep 2023 at 22:47, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Well, using emacs-debbugs and then
>>
>> C-u M-x debbugs-gnu-usertags guix-patches RET
>>
>> the list of usertags is:
>>
>> guix-patches for-core-updates
>> guix-patches reviewed-looks-good
>>
>> And if instead of guix-patches we consider guix then it reads,
>>
>> guix build-system
>> guix cross-compilation
>> guix for-core-updates
>> guix looks-good
>> guix patch
>> guix plz-work
>> guix powerpc64le-linux
>> guix ready-to-review
>> guix reproducibility
>> guix reviewed
>> guix reviewed-looks-good
>> guix test-tag
>> guix v1.3.0
> Clicking on an entry in the above list shows them; I'm sure we could
> define a procedure to directly show the bugs associated with a usertag,
> which would be useful.
Thanks.
For instance, clicking on
guix reviewed
leads to,
55997 normal,pat Tom Fitzhenry [PATCH staging 0/4] Remove texlive's dependence on mariadb.
55769 normal,pat <derekchuank@outlo [PATCH] gnu: Add xwhite.
49672 normal,pat Thiago Jung Bauerm [PATCH 0/9] Target check fixes and cleanups
where #55997 and #55769 are marked as done. How do you filter for
listing only the ones not marked as done?
Maybe, we could also automatically remove the usertag 'reviewed' when
the status is marked as 'done'. Hum, I do not know, WDYT?
Cheers,
simon
next prev parent reply other threads:[~2023-09-07 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 15:55 Process for reviewing patches as someone without commit access Christopher Baines
2023-09-06 18:17 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-06 18:19 ` Christopher Baines
2023-09-06 19:01 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-09-06 23:37 ` Simon Tournier
2023-09-06 23:59 ` Simon Tournier
2023-09-07 2:47 ` Maxim Cournoyer
2023-09-07 9:55 ` Simon Tournier [this message]
2023-09-07 16:19 ` Vagrant Cascadian
2023-09-07 19:05 ` Simon Tournier
2023-09-27 11:58 ` Christopher Baines
2023-10-04 15:46 ` Ludovic Courtès
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=87bkeemhn6.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@gmail.com \
/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).