Issue 224: Weird user interaction when a change depends on a old patch set
Reported by code-rev...@gtempaccount.com, Sep 24, 2009
Reported by Jeff Hamilton <jham@android.com> on Wed Jun 17 17:41:12 PDT 2009
Source: JIRA GERRIT-225
Affected Version: 2.0.14

If you have Gerrit change 1, with patch sets 1 and 2 and then Gerrit change 2
that depends on the git commit 1.1 and the git commit 1.2 has been submitted
to the tree Gerrit displays the dependency as MERGED when the actual git
commit that 2 depends on has not actually been merged. This has lead some
confusion when trying to submit Gerrit change 2.
Sep 24, 2009
#1 sop+code@google.com
(No comment was entered for this change.)
Status: Accepted
Owner: ---
Sep 24, 2009
#2 sop+code@google.com
(No comment was entered for this change.)
Cc: j...@android.com
Sep 28, 2009
#3 sop+code@google.com
Partially fixed by Ib7aa6c05eb539f1f1b29d517e91a2f9b5bf59a0d and also by
other changes in Ibe66d7c844141ae101a0e145f201232d0fc91f4d.

Between Ib7aa6c and Ibe66d7 we now report a much more accurate description of
the merge error when this happens and you try to submit the change whose current
patch set has the bad dependency encoded on it.

This is better, but still doesn't address the bad display of the Dependencies table,
so I'm leaving this issue open until that is also fixed.
Labels: FixedIn-2.0.22
Sep 28, 2009
#4 sop+code@google.com
(No comment was entered for this change.)
Owner: s...@google.com
Sep 28, 2009
#5 sop+code@google.com
(No comment was entered for this change.)
Status: Started
Nov 21, 2009
#6 sop@google.com
(No comment was entered for this change.)
Owner: s...@google.com