From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
Simon Tournier <zimon.toutoune@gmail.com>,
Mathieu Othacehe <othacehe@gnu.org>,
66148@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>,
Christopher Baines <guix@cbaines.net>
Subject: [bug#66148] Fix Guix version number in pulled (=most) manuals
Date: Fri, 22 Sep 2023 15:17:51 +0200 [thread overview]
Message-ID: <875y42bb40.fsf_-_@gnu.org> (raw)
In-Reply-To: <dae1caae6a5355977e6fc0d94b0c16278be206d8.1694908800.git.me@tobias.gr> (Tobias Geerinckx-Rice's message of "Sun, 17 Sep 2023 02:00:00 +0200")
Hi!
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> Now that we use the latest release VERSION even for pulled Guixes,
> make it abundantly clear that this is a later build.
>
> * guix/self.scm (info-manual): @set the PULLED flag in version.texi.
> * doc/guix.texi (Top): Honour it.
Yeah, great initiative!
I wonder if we could avoid adding code to (guix self). For instance,
we could have (guix self) leave ‘VERSION’ undefined and in the manual
we’d have those @inlineifset{VERSION, version @value{VERSION}, revision
from @command{guix pull}}.
How does that sound?
Ludo’.
next prev parent reply other threads:[~2023-09-22 13:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 23:07 [bug#66148] Fix Guix version number in pulled (=most) manuals Tobias Geerinckx-Rice via Guix-patches via
2023-09-16 23:59 ` [bug#66148] [PATCH v2 1/2] [Sloppy PoC] self: Use a more meaningful VERSION string for manuals Tobias Geerinckx-Rice via Guix-patches via
2023-09-17 0:00 ` [bug#66148] [PATCH v2 2/2] doc: Mention it when we were pulled Tobias Geerinckx-Rice via Guix-patches via
2023-09-22 13:17 ` Ludovic Courtès [this message]
2023-09-22 14:51 ` [bug#66148] Fix Guix version number in pulled (=most) manuals Tobias Geerinckx-Rice via Guix-patches via
2023-09-25 14:57 ` Ludovic Courtès
2023-09-26 5:59 ` Simon Tournier
2023-09-29 11:42 ` Tobias Geerinckx-Rice via Guix-patches via
2023-10-01 15:14 ` Ludovic Courtès
2023-09-17 0:00 ` [bug#66148] [PATCH] doc: Mention it when we were pulled Tobias Geerinckx-Rice via Guix-patches via
2023-10-14 15:34 ` Ludovic Courtès
2023-09-26 5:56 ` [bug#66148] Fix Guix version number in pulled (=most) manuals 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=875y42bb40.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=66148@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@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 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).