From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 42212@debbugs.gnu.org
Subject: bug#42212: Guix version rendered as 0.0-git in info manual
Date: Thu, 16 Jul 2020 03:12:37 +0530 [thread overview]
Message-ID: <871rlczc8i.fsf@systemreboot.net> (raw)
In-Reply-To: <878sfs9vak.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
> The “0.0-git” string comes from (guix self). As noted there, we can’t
> really afford to change the version string at each commit, or we’d have
> to rebuild the manual at each commit.
>
> We could perhaps choose a more meaningful version string, though, maybe
> by looking at the closest tag or something.
That sounds good, and `git describe` could provide us with the closest
tag. Unfortunately, (git) doesn't seem to be available during `guix
pull`. I'm trying to come up with workarounds. Do you have any ideas?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-07-15 21:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 7:59 bug#42212: Guix version rendered as 0.0-git in info manual Arun Isaac
2020-07-09 22:29 ` Ludovic Courtès
2020-07-15 21:42 ` Arun Isaac [this message]
2020-07-15 23:26 ` Ludovic Courtès
2020-07-16 0:46 ` Bengt Richter
2020-07-16 5:08 ` Bengt Richter
2020-07-16 10:06 ` zimoun
2020-07-16 9:37 ` zimoun
2020-07-16 9:48 ` Ludovic Courtès
2020-07-16 10:19 ` zimoun
2020-07-16 19:36 ` Efraim Flashner
2020-07-17 23:55 ` bug#42212: [PATCH 0/1] Use nearest tag as the version string in documentation Arun Isaac
2020-07-17 23:55 ` bug#42212: [PATCH 1/1] self: " Arun Isaac
2020-07-20 8:13 ` Ludovic Courtès
2020-07-20 8:36 ` Arun Isaac
2020-07-20 12:32 ` Ludovic Courtès
2020-07-20 13:42 ` zimoun
2020-07-27 23:13 ` bug#42212: [PATCH v2 0/1] " Arun Isaac
2020-07-27 23:13 ` bug#42212: [PATCH v2 1/1] " Arun Isaac
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=871rlczc8i.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=42212@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).