From: Marius Bakke <marius@gnu.org>
To: 50377@debbugs.gnu.org
Subject: [bug#50377] [PATCH 0/2] Support 'git describe' style commit IDs in transformations
Date: Sat, 4 Sep 2021 20:08:45 +0200 [thread overview]
Message-ID: <20210904180845.23915-1-marius@gnu.org> (raw)
The first patch makes it possible to pass a 'git describe' style commit
identifier to --with-commit. The second patch arranges so that it is
used as the package version, sans any leading 'v', if applicable.
Marius Bakke (2):
git: 'resolve-reference' handles 'git describe'-style commit IDs.
transformations: 'git describe' style commit IDs are used as version.
guix/git.scm | 37 ++++++++++++++++++++-----------------
guix/transformations.scm | 34 +++++++++++++++++++++++++---------
tests/transformations.scm | 19 +++++++++++++++++++
3 files changed, 64 insertions(+), 26 deletions(-)
--
2.31.1
next reply other threads:[~2021-09-04 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 18:08 Marius Bakke [this message]
2021-09-04 18:10 ` [bug#50377] [PATCH 1/2] git: 'resolve-reference' handles 'git describe'-style commit IDs Marius Bakke
2021-09-04 18:10 ` [bug#50377] [PATCH 2/2] transformations: 'git describe' style commit IDs are used as version Marius Bakke
2021-09-05 22:52 ` [bug#50377] [PATCH v2 1/2] git: 'resolve-reference' handles 'git describe'-style commit IDs Marius Bakke
2021-09-06 10:38 ` [bug#50377] [PATCH v3 0/2] Support 'git describe' style commit IDs in transformations Marius Bakke
2021-09-06 10:38 ` [bug#50377] [PATCH v3 1/2] git: 'resolve-reference' handles 'git describe'-style commit IDs Marius Bakke
2021-09-06 21:02 ` [bug#50377] [PATCH 0/2] Support 'git describe' style commit IDs in transformations Ludovic Courtès
2021-09-06 10:38 ` [bug#50377] [PATCH v3 2/2] transformations: 'git describe' style commit IDs are used as version Marius Bakke
2021-09-06 21:04 ` [bug#50377] [PATCH 0/2] Support 'git describe' style commit IDs in transformations Ludovic Courtès
2021-09-08 16:08 ` bug#50377: " Marius Bakke
2021-09-06 11:52 ` [bug#50377] [PATCH v3 " Xinglu Chen
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=20210904180845.23915-1-marius@gnu.org \
--to=marius@gnu.org \
--cc=50377@debbugs.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).