From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnetconf2: fixup the 'v' prefix in the version
Date: Thu, 24 Oct 2019 22:25:36 +0200 [thread overview]
Message-ID: <20191024222536.0032411f@windsurf.home> (raw)
In-Reply-To: <20191024180653.13243-1-fontaine.fabrice@gmail.com>
On Thu, 24 Oct 2019 20:06:53 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> In order for the luvi version to match what is given by
> release-monitoring.org, the 'v' prefix should be encoded in
> LIBNETCONF2_SITE and not LIBNETCONF2_VERSION.
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Sorry for missing this when reviewing/applying those packages.
Perhaps it would make sense to add a check in the check-package logic,
to verify that the version doesn't look like vX.Y.Z ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-24 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 18:06 [Buildroot] [PATCH 1/1] package/libnetconf2: fixup the 'v' prefix in the version Fabrice Fontaine
2019-10-24 20:25 ` Thomas Petazzoni [this message]
2019-10-25 6:55 ` Heiko Thiery
2019-10-25 7:30 ` Thomas Petazzoni
2019-10-25 8:06 ` Fabrice Fontaine
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=20191024222536.0032411f@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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