I am have the same error message of "fatal: ambiguous argument 'HEAD../ master': unknown revision or path not in the working tree". I too arrived at this point from fumbling with push.
magit was working great before. I could see 2 unstaged and 2 staged commits. I 'git commit'd in shell(as I don't know how to do this in magit yet!). Then in magit mode, I pressed 'P' to push, then not knowing what to put, pressed enter again without entering any arguments. I managed to push in shell with 'git push origin'. But magit is still showing errors: Unpulled commits: fatal: ambiguous argument 'HEAD../master': unknown revision or path not in the working tree. Use '--' to separate paths from revisions ... Unpushed commits: fatal: ambiguous argument '/master..HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions Do I need to set some path? Magit and git seems like great tools. Much thanks to the authors of both! Zac On Apr 7, 1:19 am, David Abrahams <[email protected]> wrote: > On Apr 6, 2009, at 3:59 PM, John Wiegley wrote: > > > > > On Apr 6, 2009, at 2:12 PM, David Abrahams wrote: > > >> I'm sure I messed something up in my Git n00b-ness, but my *magit: > >> elisp.repo* buffer looks like this: > > >> fatal: ambiguous argument 'remote/master..HEAD':unknownrevision > >> or path not in the working tree. > >> Use '--' to separate paths from revisions > > >> Can anyone help me un-bungle this? Thanks, > > > This is usually what you see if you run magit-status on the .git > > directory itself. Did this work previously? > > Absolutely, it worked! > > Backstory: Originally I had cloned my public url at GitHub, and when I > wanted to push, I fumbled around for quite a while trying to figure > out how to do the equivalent of svn switch --relocate. Eventually got > there with the help of some generous Git'ers, but clearly I left > something in a still-messed-up state. > > -- > David Abrahams > BoostPro Computinghttp://boostpro.com
