Issue 115: Automatically close changes if downloaded and then pushed directly into the branch
Status:  Released
Owner:
Closed:  Oct 2012
Reported by code-rev...@gtempaccount.com, Sep 24, 2009
Reported by Brian Swetland <swetland@android.com> on Fri Mar 27 19:06:34 PDT 2009
Source: JIRA GERRIT-115
Affected Version: 2.0.9

If a sha1 that is already in the repository is pushed as an update to a Gerrit
change, automatically close out that Gerrit change (since the patch in
question has been submitted).

The idea is, the user downloads a change, merges it locally, then pushes
directly into the branch.  During the push, the change has been implicitly
merged into the branch, so any new commits being introduced by the push should
be checked against open changes in the project.
Sep 24, 2009
#1 code-rev...@gtempaccount.com
Comment by Shawn Pearce <sop@google.com> on Sun Apr 05 12:28:00 PDT 2009

GERRIT-54 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:11:45 PDT 2009

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

Fixed in version 2.0.14.
Status: Fixed
Sep 25, 2009
#4 code-rev...@gtempaccount.com
(No comment was entered for this change.)
Labels: FixedIn-2.0.14
Oct 25, 2012
#5 sop@google.com
(No comment was entered for this change.)
Status: Released