Issue 466: Pushing to /refs/for/$BRANCH$ confuses gerrit
Status:  Released
Owner: ----
Closed:  Mar 2012
Project Member Reported by bklarson@gmail.com, Feb 24, 2010
Using 2.0.23 :(

I accidentally pushed to /refs/for/master instead of refs/for/master.  I 
think this created the actual branch refs/for/master in git.

$ git push origin HEAD:/refs/for/master
Counting objects: 15, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (8/8), 685 bytes, done.
Total 8 (delta 4), reused 0 (delta 0)
To ssh://larson@server.com:29418/path/to/repository
 * [new branch]      HEAD -> /refs/for/master

Afterwards when I pushed to refs/for/master, git just said that the remote 
was already up to date.

Deleting refs/for/master on the server and then pushing again fixed the 
problem.
Mar 4, 2010
#1 sop@google.com
C Git clients on that sort of request are asking
Gerrit to create refs/heads//refs/for/master.

Fixed in change I89d8137a89225bc31813f5870d75568e5080b059
by rejecting invalid references.
Status: Fixed
Labels: FixedIn-2.1.2
Mar 27, 2012
#2 sop@google.com
(No comment was entered for this change.)
Status: Released