[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Process for reviewing patches as someone without commit access
From: |
Simon Tournier |
Subject: |
Re: Process for reviewing patches as someone without commit access |
Date: |
Thu, 07 Sep 2023 11:55:57 +0200 |
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
Re: Process for reviewing patches as someone without commit access, Christopher Baines, 2023/09/27