What's wrong here?

180 views
Skip to first unread message

David Abrahams

unread,
Apr 6, 2009, 2:12:59 PM4/6/09
to magit
Hi,

I'm sure I messed something up in my Git n00b-ness, but my *magit:
elisp.repo* buffer looks like this:

Remote: remote nil
Local: master ~/src/elisp.repo/
Head: a704ba7... Add g-client in preparation for integration with
org or whatever

Untracked files:
.gitattributes

Unpulled commits:
fatal: ambiguous argument 'HEAD..remote/master': unknown revision
or path not in the working tree.
Use '--' to separate paths from revisions

Changes:
Modified elisp/config.d/my-loaddefs.el
...

Unpushed commits:
fatal: ambiguous argument 'remote/master..HEAD': unknown revision
or path not in the working tree.
Use '--' to separate paths from revisions

Can anyone help me un-bungle this? Thanks,

--
David Abrahams
BoostPro Computing
http://boostpro.com


John Wiegley

unread,
Apr 6, 2009, 3:59:13 PM4/6/09
to David Abrahams, magit
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': unknown revision
> 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?

John

David Abrahams

unread,
Apr 6, 2009, 8:19:30 PM4/6/09
to John Wiegley, magit


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.

Zac Zheng

unread,
Apr 15, 2009, 2:42:32 PM4/15/09
to magit
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
Reply all
Reply to author
Forward
0 new messages