all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Gabriel Hondet <gabriel.hondet@cominety.net>, 66319@debbugs.gnu.org
Subject: bug#66319: Incorrect code snippet in manual
Date: Wed, 11 Oct 2023 12:36:24 +0200	[thread overview]
Message-ID: <868r89jviv.fsf@gmail.com> (raw)
In-Reply-To: <ZRryIlJhNMsYzdhU@eryngii>

Hi,

On Mon, 02 Oct 2023 at 18:38, Gabriel Hondet via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

> The code snippets of the page 'Sending a patch series' look incorrect to
> me: the snippets mention the email address
> "guix-patches@debbugs.gnu.org" but the text mentions
> "guix-patches@gnu.org".

Yes, indeed…

> The documentation I'm looking at is the one accessible at
> https://guix.gnu.org/manual/en/html_node/Sending-a-Patch-Series.html#Multiple-Patches

…this documentation is frozen for release v1.4.0.  The current one is:

    https://guix.gnu.org/manual/devel/en/guix.html#Sending-a-Patch-Series

where it is fixed, if I read correctly.

Well the origin of your confusion is already tracked by:

        bug#51000: The Web manual situation is still needlessly confusing
        Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
        Mon, 04 Oct 2021 00:12:55 +0200
        id:87ilydycps.fsf@nckx
        https://issues.guix.gnu.org//51000
        https://issues.guix.gnu.org/msgid/87ilydycps.fsf@nckx
        https://yhetil.org/guix/87ilydycps.fsf@nckx

Therefore, I am proposing to close.  WDYT?

Cheers,
simon




  parent reply	other threads:[~2023-10-11 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 16:38 bug#66319: Incorrect code snippet in manual Gabriel Hondet via Bug reports for GNU Guix
2023-10-06 15:31 ` John Kehayias via Bug reports for GNU Guix
2023-10-11 10:36 ` Simon Tournier [this message]
2023-10-19 18:01   ` Gabriel Hondet via Bug reports for GNU Guix
2023-10-20 13:06     ` 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

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

  git send-email \
    --in-reply-to=868r89jviv.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=66319@debbugs.gnu.org \
    --cc=gabriel.hondet@cominety.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.