summaryrefslogtreecommitdiffstats
path: root/meta/recipes-multimedia/tremor/tremor_20100422.bb
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2010-09-25 01:39:02 -0400
committerSaul Wold <Saul.Wold@intel.com>2010-09-30 10:08:55 -0700
commit8d5b2224bd042940769ebffd521d68ec3eefbb55 (patch)
tree37b6a8eba47eea29c0d893aa817ad6916bcc05f9 /meta/recipes-multimedia/tremor/tremor_20100422.bb
parent06c19f0cd0c71bb721084294a2a3cb60d1855dfd (diff)
downloadpoky-8d5b2224bd042940769ebffd521d68ec3eefbb55.tar.gz
linux-wrs: validate commits when forcing branches
Fixes [BUGID #372] If for some unknown reason, the kernel git repository hasn't been properly updated and is *older* than the revisions listed in default-revisions the branch sanity checking kicks in and tries to force branches to the right revs. The problem is, the revisions it is looking for don't exist in the tree. As a result, error messages are thrown about invalid commit IDs. These aren't helpful, and are simply confusing for the user. Instead we can test for the commit ID, and if it isn't valid, indicate that the commit ID isn't valid and that the tree is potentially out of sync. This situation is not common, but it is an easy test and the extra sanity checking is useful. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta/recipes-multimedia/tremor/tremor_20100422.bb')
0 files changed, 0 insertions, 0 deletions