From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-commits@openembedded.org
Subject: Re: [oe-commits] Khem Raj : eglibc: Bump SRCREV for 2.11 and trunk recipes
Date: Fri, 14 May 2010 09:41:55 +0200 [thread overview]
Message-ID: <20100514074155.GP3370@jama> (raw)
In-Reply-To: <E1OChoj-0007ao-5h@melo.openembedded.org>
On Thu, May 13, 2010 at 11:27:49PM +0000, git version control wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: 3b41668fc1e3db2713cfa61067146cfdaf2be37a
> URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=3b41668fc1e3db2713cfa61067146cfdaf2be37a
>
> Author: Khem Raj <raj.khem@gmail.com>
> Date: Thu May 13 16:27:10 2010 -0700
>
> eglibc: Bump SRCREV for 2.11 and trunk recipes
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> ---
>
> recipes/eglibc/eglibc_2.11.bb | 2 +-
> recipes/eglibc/eglibc_svn.bb | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes/eglibc/eglibc_2.11.bb b/recipes/eglibc/eglibc_2.11.bb
> index 4f95cdc..988a9bc 100644
> --- a/recipes/eglibc/eglibc_2.11.bb
> +++ b/recipes/eglibc/eglibc_2.11.bb
> @@ -5,7 +5,7 @@ DEPENDS += "gperf-native"
> FILESPATHPKG =. "eglibc-svn:"
> PV = "2.11"
> PR = "${INC_PR}.4"
> -SVN_REV="10440"
> +SVN_REV="10454"
> EGLIBC_BRANCH="eglibc-2_11"
> SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};rev=${SVN_REV};proto=svn \
> file://eglibc-svn-arm-lowlevellock-include-tls.patch;patch=1 \
Hi,
we should probably bump PR in this case, because SVN_REV is not part of PV.
Or why not use s/SVN_REV/SRCREV/, drop ";rev=${SVN_REV}" from SRC_URI
and PR_append = "+svnr${SRCPV}"?
Thanks.
--
uin:136542059 jid:Martin.Jansa@gmail.com
Jansa Martin sip:jamasip@voip.wengo.fr
JaMa
parent reply other threads:[~2010-05-14 7:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1OChoj-0007ao-5h@melo.openembedded.org>]
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=20100514074155.GP3370@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@openembedded.org \
--cc=openembedded-devel@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