Handle multiple non-contributing commits being merged
When encountering multiple non-contributing commits included in a merge
that is TREESAME to the existing contents, ensure a list of all commits
being brought in by that merge are included in the list to be pruned
from history.
Reviewed: https:/ /review. openstack. org/408245 /git.openstack. org/cgit/ openstack/ git-upstream/ commit/ ?id=6415738c1c3 c9d26774f3e0f81 4d122f549ccf8b
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6415738c1c3c9d2 6774f3e0f814d12 2f549ccf8b
Author: Darragh Bailey <email address hidden>
Date: Wed Dec 7 17:44:32 2016 +0000
Handle multiple non-contributing commits being merged
When encountering multiple non-contributing commits included in a merge
that is TREESAME to the existing contents, ensure a list of all commits
being brought in by that merge are included in the list to be pruned
from history.
Change-Id: I643e0923f8967f 9b70d10b8796688 b782681bfe0
Closes-Bug: #1648029