From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 5/5] matchbox-keyboard: Upgrade
Date: Mon, 23 May 2016 16:36:52 +0300 [thread overview]
Message-ID: <57430774.7000805@linux.intel.com> (raw)
In-Reply-To: <1464009007.9570.21.camel@linuxfoundation.org>
On 05/23/2016 04:10 PM, Richard Purdie wrote:
>>> -SRCREV = "ebc330eac8b9d38e9aef9f01e7241c904bd01073"
>>> +SRCREV = "69d03e2aceb79cf7a616c07f8e0be4e1f9f7976b"
>>> PV = "0.0+git${SRCPV}"
>>
>> This is a good moment to start using git version tags instead of just
>> updating commit ids.
>>
>> Let's bring down the amount of 'unknown' upstream versions to zero or
>> close to it:
>>
>> http://recipes.yoctoproject.org/rrs/recipes/2.2/M1/?upstream_status=U
>> nknown#
>
> Sadly, "tags" need a network to resolve them and hence using them means
> the metadata doesn't work standalone. We can't do that.
I need to clarify: I would like the version number in PV to match an
existing upstream version tag. So that the upstream version check works
correctly.
The actual git revision for builds will continue to be determined by
commit ids in SRCREV.
Alex
next prev parent reply other threads:[~2016-05-23 13:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 12:42 [PATCH 0/5] Misc. version upgrades Jussi Kukkonen
2016-05-23 12:44 ` [PATCH 1/5] docbook-xsl-stylesheets: Upgrade 1.78.1 -> 1.79.1 Jussi Kukkonen
2016-05-24 14:59 ` Richard Purdie
2016-05-25 10:10 ` [PATCHv2] " Jussi Kukkonen
2016-05-23 12:44 ` [PATCH 2/5] dropbear: Upgrade 2015.71 -> 2016.73 Jussi Kukkonen
2016-05-23 12:44 ` [PATCH 3/5] fontconfig: Upgrade 2.11.94 -> 2.11.95 Jussi Kukkonen
2016-05-23 12:44 ` [PATCH 4/5] mesa-demos: Upgrade 8.2.0 -> 8.3.0 Jussi Kukkonen
2016-05-23 12:44 ` [PATCH 5/5] matchbox-keyboard: Upgrade Jussi Kukkonen
2016-05-23 12:56 ` Alexander Kanavin
2016-05-23 13:10 ` Richard Purdie
2016-05-23 13:36 ` Alexander Kanavin [this message]
2016-05-23 16:39 ` Richard Purdie
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=57430774.7000805@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox