all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Felix Lechner <felix.lechner@lease-up.com>,
	Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: Process for reviewing patches as someone without commit access
Date: Thu, 07 Sep 2023 01:37:56 +0200	[thread overview]
Message-ID: <86wmx2na97.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt57fa3gjdajT2ZMYhQHQ=MmoVHVoqJzFO-9vVsCudNw3SA@mail.gmail.com>

Hi Felix,

On Wed, 06 Sep 2023 at 12:01, Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:

> Usually, helpful reviews come from people with more experience. In
> your system they come from folks with less. That seems upside down to
> me.

Well, I think we are not there.  Maybe I am missing the proposal about
levels.  Somehow, I think there is not enough regular contributors for
having kind of levels.  Well, that’s not Debian. ;-)

Aside that considering how Savannah is configured today, commit access
are all or nothing.

Cheers,
simon


  reply	other threads:[~2023-09-07  0:44 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 [this message]
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

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=86wmx2na97.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --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.