Issue 1153: submitting same commit for multiple branches impossible
Status:  Released
Owner: ----
Closed:  Jul 2
Reported by oswald.b...@gmx.de, Oct 20, 2011
Affected Version:
2.2.1

What steps will reproduce the problem?
1. create a commit, including a change-id
2. push refs/for/branch1
3. push refs/for/branch2

What is the expected output? What do you see instead?
for the second push, i get a rather confusing "no new changes" message.
i would expect the commit to be actually accepted for multiple branches.
it actually works after simply changing the sha1 of the commit (i.e., commit --amend without changing anything), so this is not the old "same change-id on multiple branches" issue.


Oct 20, 2011
Project Member #1 bklarson@gmail.com
Would you mind if we closed this as a duplicate of Issue 648?
Oct 20, 2011
#2 oswald.b...@gmx.de
it may be the same underlying problem, but i cannot tell from the report; he doesn't say anything about sha1s. also, in our case, the change on the first branch was not abandoned first (iirc).
Jul 19, 2012
#4 bjoern.m...@gmail.com
https://code.google.com/p/gerrit/issues/detail?id=1142 instead of  bug 1153  (which you are reading right now)

all seem related/same rootcause/dupes
Jul 2, 2015
Project Member #5 edwin.ke...@gmail.com
Since Gerrit 2.7 you can specify a base commit on push [1] that allows you to have multiple changes for the same commit [2].

[1] https://gerrit-review.googlesource.com/Documentation/user-upload.html#base
[2] https://gerrit-review.googlesource.com/44850
Status: Released
Labels: FixedIn-2.7