summaryrefslogtreecommitdiff
path: root/meta/recipes-extended
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2010-09-08 23:18:59 -0400
committerRichard Purdie <rpurdie@linux.intel.com>2010-09-09 15:18:30 +0100
commit8fe347a851b6c22cd84532622effc3fa237efe89 (patch)
treea068e716821a166c5ff860deaab138169ac7baaa /meta/recipes-extended
parentbe74657ced5d9f31ac503b2bb846d3386fd5cb4f (diff)
downloadopenembedded-core-8fe347a851b6c22cd84532622effc3fa237efe89.tar.gz
openembedded-core-8fe347a851b6c22cd84532622effc3fa237efe89.tar.bz2
openembedded-core-8fe347a851b6c22cd84532622effc3fa237efe89.tar.xz
openembedded-core-8fe347a851b6c22cd84532622effc3fa237efe89.zip
linux-wrs: validate branches against known revisions
It is possible for the git repository to have commits on branches that are ahead of the SRCREVs for those branches. Since the kern tools will simply checkout and build, we can end up building a different kernel than what is expected. It is up to the recipe to ensure that the branches are at the correct commits. To do this, we simply check the current machine branch against the SRCREV and if they don't match we move the existing branch and do a checkout at the desired commit. Note: This probably needs to be disabled with AUTOREV. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta/recipes-extended')
0 files changed, 0 insertions, 0 deletions