summaryrefslogtreecommitdiffstats
path: root/scripts/combo-layer.conf.example
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2015-01-08 07:23:52 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-03-20 11:21:21 +0000
commitb1408ba706a9b3f597381078aa4d88d879635362 (patch)
treeab9d453a9efaca2e5cf46b93891120c318ceac5c /scripts/combo-layer.conf.example
parentfd2823d13b2d2e6436be895bd6034c185225edb6 (diff)
downloadpoky-b1408ba706a9b3f597381078aa4d88d879635362.tar.gz
combo-layer: let user choose where properties get updated
When updating a property (at the moment, only 'last_revision'), first check whether the user already added it to the main config. If so, update there even if there is a local config. This way, 'last_revision' can be shared between developers as part of the repository while still configuring per-developer repo paths outside of the git repository in a local config. An example of a repository which is set up like that is tizen-distro, with instructions for such a collaborative maintenance found here: https://review.tizen.org/git/?p=scm/bb/tizen-distro.git;a=blob;f=README;hb=refs/heads/tizen-ivi (From OE-Core rev: a3b246ee928d2ec59c8b6a775d9309f5be33ecc7) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/combo-layer.conf.example')
0 files changed, 0 insertions, 0 deletions