all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Vincent Legoll <vincent.legoll@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Guix help page
Date: Mon, 03 May 2021 14:11:15 +0000	[thread overview]
Message-ID: <tGI4oM42V_-RPNMQD-yBXi_tGQmr6ZG1kd9DtorcBI9y9lUs77gVFh_xWYC8HuoUDTfmZr4gEvQaDX8sl4wBXz6xex017pbPKMtyoI-aPzQ=@protonmail.com> (raw)
In-Reply-To: <5eox7KUlK2FQvsDgQUlY-i5cX7rzvWU-b8gm1ZEVMuSj7QGU4KEug--Rz9AegYJlK2b7B_vapaaGL8d0ZHTMqfZWtkkPUPV1kTjjBtBMCwM=@protonmail.com>

Hi,

On Monday, April 19, 2021 10:13 PM, Luis Felipe <luis.felipe.la@protonmail.com> wrote:

> On Monday, April 19, 2021 5:58 PM, Vincent Legoll vincent.legoll@gmail.com wrote:
>
> > > I'll give it a shot
> >
> > Here is an (untested) attempt, is it any good ?
>
> Personally, I would add the development version of the manual as a separate item in that page because the current Manual item already looks a bit crowded.
>
> So I'd have one item titled "GNU Guix Manual X.Y.Z" and another one titled "GNU Guix Manual Latest" (or something like that). For the former, one can use the parameter "latest-guix-version" from the "(apps base utils)" module.
>
> And I'd come up with appropriate summaries for both items.

I just sent a patch to add this (https://issues.guix.gnu.org/48187/).


  reply	other threads:[~2021-05-03 14:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 16:59 Guix help page Vincent Legoll
2021-04-19 16:44 ` Luis Felipe
2021-04-19 17:38   ` Vincent Legoll
2021-04-19 17:58     ` Vincent Legoll
2021-04-19 22:13       ` Luis Felipe
2021-05-03 14:11         ` Luis Felipe [this message]
2021-05-03 17:36           ` Vincent Legoll

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='tGI4oM42V_-RPNMQD-yBXi_tGQmr6ZG1kd9DtorcBI9y9lUs77gVFh_xWYC8HuoUDTfmZr4gEvQaDX8sl4wBXz6xex017pbPKMtyoI-aPzQ=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guix-devel@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.