unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: 66148@debbugs.gnu.org
Subject: [bug#66148] Fix Guix version number in pulled (=most) manuals
Date: Tue, 26 Sep 2023 07:59:14 +0200	[thread overview]
Message-ID: <86a5t9jwzx.fsf@gmail.com> (raw)
In-Reply-To: <87bkdq5mhl.fsf@gnu.org>

Hi,

On Mon, 25 Sep 2023 at 16:57, Ludovic Courtès <ludo@gnu.org> wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
>> Sounds good, but my main objection is to the bogus URLs and image file names.
>
> Oh right.
>
>> I considered a simpler @set RELEASE 1.4.0 that is 'manually' updated
> >on each stable & rc release, but prefer automation.  However, I'm not
>> familiar with the work of a release manager.  If they are expected to
>> run some script anyway, that could work. 

And VERSION also leads to broken URL, as with:

    @url{@value{BASE-URL}/guix-system-vm-image-@value{VERSION}.x86_64-linux.qcow2}

Cheers,
simon




  reply	other threads:[~2023-09-26  6:01 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     ` [bug#66148] Fix Guix version number in pulled (=most) manuals Ludovic Courtès
2023-09-22 14:51       ` Tobias Geerinckx-Rice via Guix-patches via
2023-09-25 14:57         ` Ludovic Courtès
2023-09-26  5:59           ` Simon Tournier [this message]
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=86a5t9jwzx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=66148@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    /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).