all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Process for reviewing patches as someone without commit access
Date: Wed, 04 Oct 2023 17:46:48 +0200	[thread overview]
Message-ID: <87ediacrvb.fsf@gnu.org> (raw)
In-Reply-To: <878r8rbys5.fsf@cbaines.net> (Christopher Baines's message of "Wed, 27 Sep 2023 12:58:19 +0100")

Hello,

Christopher Baines <mail@cbaines.net> skribis:

> That form then takes you to a page to submit the review. This can be
> done through the mailto link, or by following the manual
> instructions. Of course people using other ways of interacting with
> debbugs can also just add the reviewed-looks-good usertag for the guix
> user.
>
> Once QA has picked up that the reviewed-looks-good usertag is present,
> it'll display a dark green status and the issue will appear at the top
> of the /patches page. My hope here is that people with commit access can
> prioritise merging patches that have been reviewed and should be ready
> to merge.

Very nice, thank you!

Ludo’.


      reply	other threads:[~2023-10-04 15:51 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
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 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ediacrvb.fsf@gnu.org \
    --to=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.