all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Vincent Legoll <vincent.legoll@gmail.com>, 40597-done@debbugs.gnu.org
Subject: bug#40597: [PATCH] doc: Mention update-guix-package in guix-binary tarball, rebuild instructions.
Date: Tue, 13 Jul 2021 23:19:14 -0400	[thread overview]
Message-ID: <87pmvlpop9.fsf_-_@gmail.com> (raw)
In-Reply-To: <87sgh7jyfb.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 13 Apr 2020 15:41:12 +0200")

Hi Vincent and Ludovic,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi Vincent,
>
> Vincent Legoll <vincent.legoll@gmail.com> skribis:
>
>>>>From dd961656d9bd98d11ba5e38be89cd1952fefc263 Mon Sep 17 00:00:00 2001
>> From: Vincent Legoll <vincent.legoll@gmail.com>
>> Date: Mon, 13 Apr 2020 14:25:57 +0200
>> Subject: [PATCH] doc: Mention update-guix-package in guix-binary tarball
>>  rebuild instructions.
>>
>> * doc/guix.texi (Binary Installation): Mention 'make update-guix-package'.
>
> I agree this needs to be documented, but I don’t think this is the right
> place: “Binary Installation” is for users who want to install.  Instead,
> we should document it in a section explicitly targeting Guix developers,
> maybe under “Contributing”?

A "Updating the Guix Package" subsection has since been added to the
Contributing section, which I believe covers this.

Thank you,

Closing.

Maxim




      parent reply	other threads:[~2021-07-14  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 12:34 [bug#40597] [PATCH] doc: Mention update-guix-package in guix-binary tarball, rebuild instructions Vincent Legoll
2020-04-13 13:41 ` Ludovic Courtès
2020-04-13 13:43   ` Vincent Legoll
2021-07-14  3:19   ` Maxim Cournoyer [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=87pmvlpop9.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=40597-done@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=vincent.legoll@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 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.