diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2015-01-08 07:23:52 -0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-03-20 11:03:08 +0000 |
| commit | a3b246ee928d2ec59c8b6a775d9309f5be33ecc7 (patch) | |
| tree | 16f14b5bc9b3f824da1eb1e6be875c1936225f5c /scripts/test-remote-image | |
| parent | fdd2e0c1baa80106d26236cb734e0d9a98e3fdac (diff) | |
| download | openembedded-core-a3b246ee928d2ec59c8b6a775d9309f5be33ecc7.tar.gz openembedded-core-a3b246ee928d2ec59c8b6a775d9309f5be33ecc7.tar.bz2 openembedded-core-a3b246ee928d2ec59c8b6a775d9309f5be33ecc7.zip | |
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
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts/test-remote-image')
0 files changed, 0 insertions, 0 deletions