summaryrefslogtreecommitdiff
path: root/meta
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-09 22:25:48 +0100
commit701bcd52c208f22a9a6c48a11a35bcf1c4e413df (patch)
tree458c0a553ceac46459ec2d741a0fa36a10ba067a /meta
parent8ffcdcc53bac64c62478fbb72d817c842dde8b28 (diff)
downloadopenembedded-core-701bcd52c208f22a9a6c48a11a35bcf1c4e413df.tar.gz
openembedded-core-701bcd52c208f22a9a6c48a11a35bcf1c4e413df.tar.bz2
openembedded-core-701bcd52c208f22a9a6c48a11a35bcf1c4e413df.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. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta')
0 files changed, 0 insertions, 0 deletions