Issue 947: Push to non-connected destination branch possible
Status:  Released
Owner: ----
Closed:  May 2011
Project Member Reported by stefanl...@gmail.com, May 17, 2011
Affected Version:

What steps will reproduce the problem?
1. Create a commit on a branch not connected to origin/master, e.g. refs/meta/config
2. Push it to Gerrit to refs/for/master
3. A new change is created. This change cannot be merged in the end.

What is the expected output? What do you see instead?
An error "no common ancestry" is expected when trying to push.


Please provide any additional information below.
In the class RecieveCommit, method parseNewChangeCommand, there is a check if the new commit is connected to any HEAD or tag which is advertised to the user. It should instead check if it is connected to the target branch.

May 18, 2011
#1 sop@google.com
(No comment was entered for this change.)
Status: Submitted
Labels: FixedIn-2.1.7
May 31, 2011
#2 sop@google.com
(No comment was entered for this change.)
Status: Released