From: Saul Wold <sgw@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] btrfs-tools: added PV to git package recipe
Date: Fri, 01 Mar 2013 11:11:37 -0800 [thread overview]
Message-ID: <5130FD69.1020804@linux.intel.com> (raw)
In-Reply-To: <1362141704.1055.56.camel@ted>
On 03/01/2013 04:41 AM, Richard Purdie wrote:
> On Fri, 2013-03-01 at 14:19 +0200, Emilia Ciobanu wrote:
>> Signed-off-by: Emilia Ciobanu <emilia.maria.silvia.ciobanu@intel.com>
>> ---
>> .../btrfs-tools/btrfs-tools_git.bb | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
>> index e963a74..df216b1 100644
>> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
>> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_git.bb
>> @@ -17,6 +17,8 @@ SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git;p
>>
>> S = "${WORKDIR}/git"
>>
>> +PV = "0.20-rc1+git${SRCPV}"
>> +
>> PR = "r6"
>
> Sadly this won't allow an upgrade path to 0.20 when its released.
>
> We'd either need to use 0.20~rc1 or 0.19+0.20-rc1 as the string.
I would suggest the 0.20~rc1 variation since the Git Rev we are at is
already beyong 0.20-rc1 tag.
Sau!
>
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2013-03-01 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 12:19 [PATCH v2] btrfs-tools: added PV to git package recipe Emilia Ciobanu
2013-03-01 12:41 ` Richard Purdie
2013-03-01 19:11 ` Saul Wold [this message]
2013-03-01 19:24 ` Martin Jansa
2013-03-01 23:09 ` Burton, Ross
2013-03-01 23:19 ` Richard Purdie
2013-03-01 23:46 ` Richard Purdie
2013-03-04 8:42 ` Ciobanu, Emilia Maria Silvia
2013-03-04 10:03 ` Richard Purdie
2013-03-04 11:13 ` Ciobanu, Emilia Maria Silvia
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=5130FD69.1020804@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.