Active
Project:
Git on Drupal.org
Component:
Git
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Mar 2011 at 09:08 UTC
Updated:
16 Feb 2012 at 12:22 UTC
I created a new project following the instructions on the new project git tab.
Then:
~/Sites/_sandbox/content_push joachim$ git push origin master
Counting objects: 7, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 4.40 KiB, done.
Total 7 (delta 0), reused 0 (delta 0)
To joachim@git.drupal.org:project/content_push.git
* [new branch] master -> master
~/Sites/_sandbox/content_push joachim$ git checkout -b 6.x-1.x
Switched to a new branch '6.x-1.x'
~/Sites/_sandbox/content_push joachim$ git push origin 6.x-1.x
Total 0 (delta 0), reused 0 (delta 0)
fatal: bad revision '^{master}'
To joachim@git.drupal.org:project/content_push.git
* [new branch] 6.x-1.x -> 6.x-1.x
~/Sites/_sandbox/content_push joachim$
Comments
Comment #1
joachim commentedAnd now this happens:
Comment #2
joachim commented... and yet my commit appears on d.org !?!?!
Comment #3
joachim commentedI cloned onto another machine and the branch didn't appear. Trying to create it got me this when I pushed:
~/Sites/_sandbox/form_email_confirmation joachim$ git push origin 6.x-1.x
Total 0 (delta 0), reused 0 (delta 0)
fatal: bad revision '^{master}'
To joachim@git.drupal.org:project/form_email_confirmation.git
* [new branch] 6.x-1.x -> 6.x-1.x
Comment #4
eliza411 commentedThere's a fix for this, but there is no adequate environment for testing the fix before deployment and no actual deployment process. Since it's ugly and confusing, but it doesn't actually break anything, this is postponed until there's a reasonable procedure in place.
Comment #5
rfayThis is easy enough to demonstrate, so marking it active. #1075506: fatal: bad revision '^{master}' when pushing a branch (duplicate of this one) has instructions on how to recreate.
Comment #6
eliza411 commented@rfay I'm guessing after a year this probably isn't critical; any idea if this is still happening?
Comment #7
rfayIt never was critical, as it was a bogus error message.
I'd be surprised if it got fixed, but I haven't seen it lately.