Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: John Keeping <john@metanate.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/fscryptctl: bump to v1.0.0
Date: Fri, 22 Jul 2022 14:47:33 +0200	[thread overview]
Message-ID: <20220722144733.50446ab3@windsurf> (raw)
In-Reply-To: <20220722110103.4068083-1-john@metanate.com>

Hello John,

On Fri, 22 Jul 2022 12:01:03 +0100
John Keeping <john@metanate.com> wrote:

> -FSCRYPTCTL_VERSION = f037dcf4354ce8f25d0f371b58dfe7a7ac27576f
> +FSCRYPTCTL_VERSION = v1.0.0
>  FSCRYPTCTL_SITE = $(call github,google,fscryptctl,$(FSCRYPTCTL_VERSION))

Thanks a lot!

However, we want this to look like this:

 FSCRYPTCTL_VERSION = 1.0.0
 FSCRYPTCTL_SITE = $(call github,google,fscryptctl,v$(FSCRYPTCTL_VERSION))

This allows the version field to properly match against values reported
by release-monitoring.org, thanks to not having the "v" prefix.

This will need an update in the hash file, of course, as the tarball
name will also be without the "v".

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-07-22 12:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 11:01 [Buildroot] [PATCH] package/fscryptctl: bump to v1.0.0 John Keeping
2022-07-22 12:47 ` Thomas Petazzoni via buildroot [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220722144733.50446ab3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=john@metanate.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox