From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] opkg-utils: update SRCREV
Date: Thu, 2 Jun 2016 15:04:25 -0500 [thread overview]
Message-ID: <57509149.2050405@ni.com> (raw)
In-Reply-To: <63886.10.252.18.48.1464898545.squirrel@linux.intel.com>
On 06/02/2016 03:15 PM, alexander.kanavin@linux.intel.com wrote:
>> Drop patches now included in newer SRCREV. Update HOMEPAGE and PV
>> version to better align with opkg. Current revision include:
>> +SRCREV = "ecd9a499d336ffd127bda3c5ba403f0a5ca056a5"
>> +PV = "0.3.1+git${SRCPV}"
>
> PV should match an existing version tag in the repository, and currently
> there are no tags at all. Please start tagging the versions there,
> otherwise there is no link between the version and the commit id in the
> upstream.
opkg-utils, as you mentioned, has never had any tags because it has never had a
proper release. The previous PV was pretty arbitrary too (I believe it was based
on the opkg version being used at the time).
But I like the idea of more tightly coupling opkg and opkg-utils via the
version. Since I am tagging opkg 0.3.2 in a couple of weeks, I'll bump the PV of
opkg-utils to 0.3.2 and will tag the latest commit to 0.3.2.
--
Cheers,
Alejandro
next prev parent reply other threads:[~2016-06-02 20:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 18:33 [PATCH] opkg-utils: update SRCREV Alejandro del Castillo
2016-06-02 20:15 ` alexander.kanavin
2016-06-02 20:04 ` Alejandro del Castillo [this message]
2016-06-02 20:23 ` [PATCH v2] " Alejandro del Castillo
2016-06-03 6:47 ` Richard Purdie
2016-06-03 21:54 ` Alejandro del Castillo
2016-06-06 16:08 ` [PATCH v3] " Alejandro del Castillo
-- strict thread matches above, loose matches on Subject: below --
2014-12-18 21:03 [PATCH] opkg-utils: Update SRCREV Paul Barker
2014-07-31 21:38 Paul Barker
2014-07-31 21:38 ` Paul Barker
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=57509149.2050405@ni.com \
--to=alejandro.delcastillo@ni.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.