From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: SRCPV always upgradeable paths for git recipes
Date: Wed, 11 Nov 2009 10:45:11 -0500 [thread overview]
Message-ID: <20091111154511.GA2761@denix.org> (raw)
In-Reply-To: <1257953228-2353-1-git-send-email-Martin.Jansa@gmail.com>
On Wed, Nov 11, 2009 at 04:27:08PM +0100, Martin Jansa wrote:
> * Holger Hans Peter Freyther <zecke@openmoko.org> did for the OM git
> tree that was never merged back into OE.
> * Taken from xora/angstrom-srcpv branch where it rot for long enough
We also discussed it during the OEDEM...
--
Denys
> ---
> conf/bitbake.conf | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/conf/bitbake.conf b/conf/bitbake.conf
> index 39a1f27..7c0defe 100644
> --- a/conf/bitbake.conf
> +++ b/conf/bitbake.conf
> @@ -570,7 +570,8 @@ UPDATECOMMAND_cvs = "/usr/bin/env 'PATH=${PATH}' cvs -d${CVSROOT} update -d -P $
> UPDATECOMMAND_svn = "/usr/bin/env svn update ${SVNCOOPTS}"
> SRCDATE = "${DATE}"
> SRCREV = "1"
> -AUTOREV = "${@bb.fetch.get_srcrev(d)}"
> +SRCPV = "${@bb.fetch.get_srcrev(d)}"
> +AUTOREV = "${SRCPV}"
>
> SRC_URI = "file://${FILE}"
>
> --
> 1.6.5.2
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2009-11-11 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 15:27 [PATCH] bitbake.conf: SRCPV always upgradeable paths for git recipes Martin Jansa
2009-11-11 15:37 ` Graeme Gregory
2009-11-12 9:10 ` Martin Jansa
2009-11-11 15:45 ` Denys Dmytriyenko [this message]
2009-11-11 17:43 ` Martin Jansa
2009-11-11 18:42 ` Philip Balister
2009-11-11 21:15 ` Richard Purdie
2009-11-11 21:49 ` Phil Blundell
2009-11-11 22:57 ` Philip Balister
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=20091111154511.GA2761@denix.org \
--to=denis@denix.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 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.