summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/python/python3
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2015-05-08 14:37:30 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-05-29 13:00:42 +0100
commit1bc46199e569411150b050818ff17abc66f899f2 (patch)
treef12517fea362cbcccdc89b103715defcaf1e2efd /meta/recipes-devtools/python/python3
parent2abacf00ee3f60735bf7c0dc7130c72267822b30 (diff)
downloadopenembedded-core-1bc46199e569411150b050818ff17abc66f899f2.tar.gz
openembedded-core-1bc46199e569411150b050818ff17abc66f899f2.tar.bz2
openembedded-core-1bc46199e569411150b050818ff17abc66f899f2.zip
combo-layer: improve merge commit handling
When the head of a branch is a merge commit, combo-layer did not record that commit as last_revision because it only considers applied patches, and the merge commit never gets applied. This causes problems when the merge commit leads to multiple patches and the commit id that gets recorded only reaches some of these patches. The next run then will try to re-apply the other patches. This special case is now detected and dealt with by bumping last_revision to the branch commit. The behavior where the head is a normal commit is intentionally not changed, because some users might prefer the traditional behavior. (From OE-Core rev: 701bcd52c208f22a9a6c48a11a35bcf1c4e413df) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python/python3')
0 files changed, 0 insertions, 0 deletions