summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-manual
diff options
context:
space:
mode:
authorDarren Hart <dvhart@linux.intel.com>2011-05-25 20:47:05 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-05-27 16:38:53 +0100
commit3a454781dffcb63d1c0970f4b441e57603a1b79e (patch)
tree0900b8d6277a0c45f465566523357be952fd36a2 /documentation/kernel-manual
parent7f75045371f24acee863da378d94bf4e724b8731 (diff)
downloadpoky-3a454781dffcb63d1c0970f4b441e57603a1b79e.tar.gz
u-boot: rename u-boot_git.bb to u-boot_${PV}.bb
In order to facilitate reuse of the oe-core u-boot recipe, there needs to be some assurance that the oe-core version won't change without a clear indicator to people extending it. By renaming the recipe to include its version string instead of "git", BSP layers can extend a specific base version of u-boot, ie. u-boot_2011.03.bbappend. When 2011.06 becomes available, we can create that file without instantly breaking all the BSPs depending on oe-core version of the recipe. As a matter of policy I would recommend we not carry more than 2 versioned u-boot recipess at any given time. This will provide BSP layers time to migrate to the newer version, without cluttering oe-core with numerous stale versions of u-boot. We may decide later to resurrect u-boot_git.bb as an AUTOREV recipe to faciliate upstream development on u-boot in the oe environment. (From OE-Core rev: f788d4b503ecc6600612746c4936dfb9393e237c) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Koen Kooi <koen@dominion.thruhere.net> Cc: Jason Kridner <jkridner@beagleboard.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-manual')
0 files changed, 0 insertions, 0 deletions