Go to file
Jan Opacki b22ee233f1 Fix change stuck in SUBMITTED state but actually merged
This behavior is caused by submitting a commit that has a tag.
Method MergeUtil.markCleanMerges is used by each merge strategy
to update the status of a change if it was a clean merge. It skips
commits that are identified as accepted and their entire ancestry
chain. If a commit is tagged, method MergeOp.getAlreadyAccepted
identifies it as accepted (even if it is not merged yet).
Fix prevents a commit that is referred by a tag to be included in
alreadyAccepted set. If such commit is already merged then it will
be covered anyway by adding heads to alreadyAccepted.

Add a corresponding test that pushes a commit with a tag

Bug: Issue 600
Change-Id: If00247b809b985eaf60ef5ef09fad0f475fb06b9
2013-08-15 10:30:05 +02:00
2013-08-06 11:34:13 -07:00
2013-07-26 18:11:51 -07:00
2013-05-21 20:28:56 -07:00
2013-05-21 20:28:56 -07:00
2013-05-21 20:28:56 -07:00
2013-05-21 20:28:56 -07:00
2013-07-05 18:55:30 -07:00
2013-05-21 20:28:56 -07:00
2013-08-06 18:37:45 -07:00
2013-07-30 17:18:33 +00:00
2008-11-14 16:59:34 -08:00
2009-03-27 20:20:10 -07:00
Description
RETIRED, Gerrit as used by OpenStack
120 MiB