Issue 54: if a change is revised and the sha of the new commit matches a commit in the tree, move it to submitted
Status:  Released
Owner:
Closed:  Oct 2012
Reported by code-rev...@gtempaccount.com, Sep 24, 2009
Reported by Brian Swetland <swetland@android.com> on Wed Jan 28 18:05:44 PST 2009
Source: JIRA GERRIT-54
Affected Version: 2.0

For the kernel workflow, we often will pull down changes, cherry-pick/reorder
them, test them, then push them up as a unit.

It would be nice to be able to close out open changes by pushing an update to
them of the version of the change that made it into the tree.  Maybe in the
future this could be further automated by tagging changes with a Gerrit-ID:
field too.
Sep 24, 2009
#1 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Sun Apr 05 12:27:45 PDT 2009

GERRIT-115 is related in that it is the opposite direction of this.
Sep 24, 2009
#2 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Sat Jun 13 16:59:06 PDT 2009

Fixed by https://review.source.android.com/10378
Sep 24, 2009
#3 code-rev...@gtempaccount.com
Update by Shawn Pearce <sop@google.com> on Sat Jun 13 16:59:06 PDT 2009

Fixed in version 2.0.14.
Status: Fixed
Sep 24, 2009
#4 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Sat Jun 13 17:03:12 PDT 2009

Only the push commit to change is implemented, I didn't do the Gerrit-ID
pattern match described in this issue, because that is actually more related
to GERRIT-115 (where the change is closed when the commit is pushed into a
branch).
Sep 25, 2009
#5 code-rev...@gtempaccount.com
(No comment was entered for this change.)
Labels: FixedIn-2.0.14
Oct 25, 2012
#6 sop@google.com
(No comment was entered for this change.)
Status: Released