unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: Marius Bakke <marius@gnu.org>, 50377@debbugs.gnu.org
Subject: [bug#50377] [PATCH v3 0/2] Support 'git describe' style commit IDs in transformations
Date: Mon, 06 Sep 2021 13:52:27 +0200	[thread overview]
Message-ID: <8735qh3oqs.fsf@yoctocell.xyz> (raw)
In-Reply-To: <20210906103846.14941-1-marius@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 669 bytes --]

On Mon, Sep 06 2021, Marius Bakke wrote:

> * The new resolve-reference condition actually returns.
> * The transformation code now use the same heuristics as
>   resolve-reference to check for the 'describe' style.
>
> I'm now reasonably confident in these patches and will push in a day or
> two unless there are objections.  :-)
>
> Marius Bakke (2):
>   git: 'resolve-reference' handles 'git describe'-style commit IDs.
>   transformations: 'git describe' style commit IDs are used as version.

I haven’t looked at the patch itself, but maybe it’s worthing mentioning
this in the “9.1.2 Package Transformation Options” section in the manual?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      parent reply	other threads:[~2021-09-06 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-04 18:08 [bug#50377] [PATCH 0/2] Support 'git describe' style commit IDs in transformations Marius Bakke
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   ` Xinglu Chen [this message]

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=8735qh3oqs.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=50377@debbugs.gnu.org \
    --cc=marius@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).