From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, 66148@debbugs.gnu.org
Subject: [bug#66148] Fix Guix version number in pulled (=most) manuals
Date: Fri, 22 Sep 2023 14:51:44 +0000 [thread overview]
Message-ID: <74D0DE30-C47C-47C7-8CE9-0919E8D43EE1@tobias.gr> (raw)
In-Reply-To: <875y42bb40.fsf_-_@gnu.org>
Sounds good, but my main objection is to the bogus URLs and image file names.
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.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2023-09-22 14:53 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74D0DE30-C47C-47C7-8CE9-0919E8D43EE1@tobias.gr \
--to=guix-patches@gnu.org \
--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 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.