From: Robert Yang <liezhi.yang@windriver.com>
To: <alexander.kanavin@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 4/5] btrfs-tools: 4.1.1 -> 4.1.2
Date: Sat, 22 Aug 2015 16:33:33 +0800 [thread overview]
Message-ID: <55D833DD.4070400@windriver.com> (raw)
In-Reply-To: <58077.10.252.47.114.1440163323.squirrel@linux.intel.com>
On 08/21/2015 09:22 PM, alexander.kanavin@linux.intel.com wrote:
>>> Is there no PV change here?
>>
>> Thanks, I updated in the repo.
>> -PV = "4.1.1+git${SRCPV}"
>> +PV = "4.1.2+git${SRCPV}"
>
> You can also rename the recipe to btrfs-tools_4.1.2.bb and remove the PV
> altogether. The above form is only needed if you're taking something from
> git that is not a pristine tagged release (i.e. when it is a tagged
> commit+additional commits).
Thanks, updated in the repo:
git://git.openembedded.org/openembedded-core-contrib rbt/PU
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/PU
Robert Yang (4):
gnupg: 2.1.6 -> 2.1.7
gnu-efi: 3.0.2 -> 3.0.3
btrfs-tools: 4.1.1 -> 4.1.2
oprofile: 1.0.0 -> 1.1.0
// Robert
>
> Alex
>
>
next prev parent reply other threads:[~2015-08-22 8:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 10:15 [PATCH 0/5] Packages Upgrade Robert Yang
2015-08-21 10:15 ` [PATCH 1/5] gnupg: 2.1.6 -> 2.1.7 Robert Yang
2015-08-21 10:15 ` [PATCH 2/5] man-pages: 4.01 -> 4.02 Robert Yang
2015-08-21 10:45 ` Jussi Kukkonen
2015-08-21 10:54 ` Robert Yang
2015-08-21 10:15 ` [PATCH 3/5] gnu-efi: 3.0.2 -> 3.0.3 Robert Yang
2015-08-21 10:15 ` [PATCH 4/5] btrfs-tools: 4.1.1 -> 4.1.2 Robert Yang
2015-08-21 10:47 ` Jussi Kukkonen
2015-08-21 10:54 ` Robert Yang
2015-08-21 13:22 ` alexander.kanavin
2015-08-22 8:33 ` Robert Yang [this message]
2015-08-21 10:15 ` [PATCH 5/5] oprofile: 1.0.0 -> 1.1.0 Robert Yang
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=55D833DD.4070400@windriver.com \
--to=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox