unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: reza <reza@housseini.me>, 74736@debbugs.gnu.org, ludo@gnu.org
Cc: "Noé Lopez" <noe@xn--no-cja.eu>, "Noé Lopez" <noelopez@free.fr>,
	"Christopher Baines" <mail@cbaines.net>
Subject: [bug#74736] [PATCH v6] Add Request-for-Comments process.
Date: Fri, 10 Jan 2025 00:22:05 +0100	[thread overview]
Message-ID: <87y0zjh8te.fsf@gmail.com> (raw)
In-Reply-To: <01020194449ea437-ba0e47aa-a66a-43a0-9ba8-bdad0f257714-000000@eu-west-1.amazonses.com>

Hi,

On Wed, 08 Jan 2025 at 06:33, reza via Guix-patches via <guix-patches@gnu.org> wrote:

> As a maybe tangential comment: There is no mention of an identifier
> for an RFC (e.g. PEP number) or a unique string to identify or
> reference it?

I think there is one: the first one is 001 and then they will be
incremented.  For instance, assuming v6, it would be: RFC 001, or RFC
001-rfc-process.

Is it clearer?

Cheers,
simon




  reply	other threads:[~2025-01-09 23:57 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 12:29 [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Noé Lopez via Guix-patches via
2024-12-08 12:31 ` [bug#74736] [PATCH v2 1/1] rfc: " Noé Lopez via Guix-patches via
2024-12-12 18:14   ` [bug#74736] [PATCH v2 0/1] " Ludovic Courtès
2024-12-12 19:47     ` Simon Tournier
2024-12-14 10:06       ` Ludovic Courtès
2024-12-23 17:58         ` Simon Tournier
2024-12-26 11:15           ` Ludovic Courtès
2024-12-09 20:47 ` Artyom V. Poptsov
2024-12-12 19:30 ` [bug#74736] [PATCH v3] rfc: " Simon Tournier
2024-12-14 10:47   ` Ludovic Courtès
2024-12-22 13:06   ` Noé Lopez via Guix-patches via
2024-12-22 13:56 ` [bug#74736] [PATCH v4 0/1] " Noé Lopez via Guix-patches via
2024-12-22 13:56   ` [bug#74736] [PATCH v4 1/1] " Noé Lopez via Guix-patches via
2024-12-23 14:42     ` [bug#74736] [PATCH v2 0/1] " Ludovic Courtès
2024-12-23 17:33       ` Simon Tournier
2024-12-26 11:28         ` Ludovic Courtès
2024-12-31 15:23           ` Simon Tournier
2024-12-29 18:31       ` Noé Lopez via Guix-patches via
2024-12-30 11:03         ` Ludovic Courtès
2024-12-30 11:58           ` Noé Lopez via Guix-patches via
2025-01-04 17:28             ` Ludovic Courtès
2025-01-05 12:51               ` Noé Lopez via Guix-patches via
2025-01-06 10:29                 ` Simon Tournier
2025-01-06 17:40                 ` Ludovic Courtès
2025-01-08 10:53               ` Ludovic Courtès
2025-01-09 13:27                 ` Ludovic Courtès
2025-01-09 22:48                   ` Simon Tournier
2025-01-03 18:14 ` [bug#74736] [PATCH v5] rfc: " Simon Tournier
2025-01-06 22:29   ` [bug#74736] [PATCH v6] Add Request-for-Comments process Ludovic Courtès
2025-01-07 17:06     ` Noé Lopez via Guix-patches via
2025-01-08 15:12       ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Suhail Singh
2025-01-09 17:21         ` Simon Tournier
     [not found]     ` <825F8319-4F41-4F4C-81B3-2C84A73A13CF@housseini.me>
2025-01-08  6:33       ` [bug#74736] [PATCH v6] Add Request-for-Comments process reza via Guix-patches via
2025-01-09 23:22         ` Simon Tournier [this message]
2025-01-08 16:26     ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process pukkamustard
2025-01-09 17:18       ` Simon Tournier
2025-01-09 21:00         ` Ludovic Courtès
2025-01-09 21:16       ` Ludovic Courtès
2025-01-09 16:21     ` [bug#74736] [PATCH v6] Add Request-for-Comments process Simon Tournier
2025-01-09 22:32       ` [bug#74736] [PATCH v2 0/1] Add Request-For-Comment process Ludovic Courtès
2025-01-09 23:56         ` Simon Tournier
2025-01-10  0:40     ` [bug#74736] [PATCH v6] Add Request-for-Comments process Vagrant Cascadian
2025-01-10  7:44     ` Janneke Nieuwenhuizen
2025-01-07 19:40 ` [bug#74736] Add Request-For-Comment process Ricardo Wurmus
2025-01-09 23:45 ` [bug#74736] [PATCH v7] Add Guix Common Document process Simon Tournier

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=87y0zjh8te.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=74736@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=noe@xn--no-cja.eu \
    --cc=noelopez@free.fr \
    --cc=reza@housseini.me \
    /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).