On Tue, Oct 29, 2013 at 3:20 PM, Hans Beckérus hans.becke...@gmail.com wrote:
On Tue, Oct 29, 2013 at 2:42 PM, Martin Jansa martin.ja...@gmail.com wrote:
On Tue, Oct 29, 2013 at 02:27:30PM +0100, Hans Beckérus wrote:
On Tue, Oct 29, 2013 at 12:00 PM, Martin Jansa martin.ja...@gmail.com
wrote:
On Tuesday 05 November 2013 10:25:24 Hans Beckérus wrote:
I have seen recipes that defines PV = xyz+git${SRCPV} and then
SRCREV to a specific tag instead of ${AUTOREV}.
Is that not contradictory? Or is it simply that the author of that
recipe wished to have a git tag automatically added to the
-Original Message-
From: Paul Eggleton paul.eggle...@linux.intel.com
AFAIK, there are two recommended values for SRCREV assuming you are
fetching
from an SCM at all:
A) A specific revision (SHA1 hash when fetching from git)
or
B) ${AUTOREV} if you want to always build the latest
On 2013-11-05 11:10, Robert Calhoun wrote:
-Original Message-
From: Paul Eggleton paul.eggle...@linux.intel.com
AFAIK, there are two recommended values for SRCREV assuming you are
fetching
from an SCM at all:
A) A specific revision (SHA1 hash when fetching from git)
or
B)
On Tue, Oct 29, 2013 at 12:46:18PM +0100, Hans Beckérus wrote:
Hi. I am wondering if we are using SRCREV wrong somehow.
Is it expected that if we use SRCREV = ${AUTOREV}, that any changes
to the remote should be automatically detected and downloaded/fetched?
I can no see that this is actually
On Tue, Oct 29, 2013 at 12:00 PM, Martin Jansa martin.ja...@gmail.com wrote:
On Tue, Oct 29, 2013 at 12:46:18PM +0100, Hans Beckérus wrote:
Hi. I am wondering if we are using SRCREV wrong somehow.
Is it expected that if we use SRCREV = ${AUTOREV}, that any changes
to the remote should be
On Tue, Oct 29, 2013 at 02:27:30PM +0100, Hans Beckérus wrote:
On Tue, Oct 29, 2013 at 12:00 PM, Martin Jansa martin.ja...@gmail.com wrote:
On Tue, Oct 29, 2013 at 12:46:18PM +0100, Hans Beckérus wrote:
Hi. I am wondering if we are using SRCREV wrong somehow.
Is it expected that if we use
