unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Leo Famulari <leo@famulari.name>
Cc: guix-maintainers@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Christopher Baines" <mail@cbaines.net>,
	61894@debbugs.gnu.org, 宋文武 <iyzsong@envs.net>,
	"Andreas Enge" <andreas@enge.fr>,
	guix-devel@gnu.org
Subject: [bug#61894] [PATCH RFC] Team approval for patches
Date: Thu, 09 Mar 2023 09:48:21 +0100	[thread overview]
Message-ID: <86v8janwdm.fsf@gmail.com> (raw)
In-Reply-To: <874jqvul1v.fsf@gmail.com>

Hi,

On Wed, 08 Mar 2023 at 13:58, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

> number of their R package updates (thanks!)).  It seems starting to use
> the 'Reviewed-by' git message tag would make this easy to account for.

Quoting from thread [1]:

        I agree that Reviewed-by would be helpful.

        Once reviewed, the author or the reviewer could roll the count and
        re-send the patch (or series), applying the line Reviewed-by.

        It would reward the reviewer for their work.  And it would help the
        committer work.

Subject: Thoughts on committers pushing simple changes from other committers?
1: <https://yhetil.org/guix/86k00avhpv.fsf@gmail.com>

Cheers,
simon




  parent reply	other threads:[~2023-03-09  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 16:13 [bug#61894] [PATCH RFC] Team approval for patches Ludovic Courtès
     [not found] ` <871qm8wf8e.fsf@cbaines.net>
2023-03-01 19:21   ` Felix Lechner via Guix-patches via
2023-03-01 22:45   ` Ludovic Courtès
2023-03-02 11:04     ` Andreas Enge
2023-03-07  1:53     ` 宋文武 via Guix-patches via
     [not found]       ` <ZAcTw6I31Rl3nRDE@jurong>
     [not found]         ` <861qm0da4y.fsf@gmail.com>
2023-03-07 18:29           ` Maxim Cournoyer
2023-03-07 22:40             ` Leo Famulari
     [not found]               ` <874jqvul1v.fsf@gmail.com>
2023-03-09  8:48                 ` Simon Tournier [this message]
     [not found]             ` <ZAhRg7BjytZGGB5O@3900XT>
     [not found]               ` <878rg7uqb4.fsf@gmail.com>
     [not found]                 ` <86lek6ntpb.fsf@gmail.com>
     [not found]                   ` <874jqtte7c.fsf@gmail.com>
     [not found]                     ` <87bkl0frnk.fsf@gnu.org>
     [not found]                       ` <87356ar6p1.fsf@gmail.com>
     [not found]                         ` <87bkku2e14.fsf@gnu.org>
2023-03-17 15:46                           ` Maxim Cournoyer

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=86v8janwdm.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=61894@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=iyzsong@envs.net \
    --cc=leo@famulari.name \
    --cc=ludo@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).