From: Mathias Lafeldt <misfire@debugon.org>
To: Todd Wells <ttopwells@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: fatal: ambiguous argument 'HEAD^': unknown revision or path not in the working tree.
Date: Thu, 28 Oct 2010 15:42:32 +0200 [thread overview]
Message-ID: <4CC97DC8.1010508@debugon.org> (raw)
In-Reply-To: <loom.20101028T150254-457@post.gmane.org>
Todd Wells wrote:
> I was using GitX to prepare a commit. Something happened -- I don't
> know what -- and suddenly my branch only had a single commit
> in it that appears to contain all the files in my tree. So I went to the
> command line and did this:
>
> $ git reset --soft HEAD^
> fatal: ambiguous argument 'HEAD^': unknown revision or path not
> in the working tree.
>
> When I do 'git log' in this branch, there's only one commit. Now, I
> had many commits in this branch a few minutes ago. I really,
> really, don't want to lose this.
>
> What steps should I take to attempt to recover?
Check if you can reset your HEAD to a previous state saved in your
(local) reflog.
See section "RefLog Shortnames" in http://progit.org/book/ch6-1.html
-Mathias
next prev parent reply other threads:[~2010-10-28 13:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 13:09 fatal: ambiguous argument 'HEAD^': unknown revision or path not in the working tree Todd Wells
2010-10-28 13:41 ` SZEDER Gábor
2010-10-28 13:42 ` Mathias Lafeldt [this message]
2010-10-28 13:42 ` Santi Béjar
[not found] ` <AANLkTi=QODz+Gf9hwrdu6b900CzuO-BBnF2zmLWOGFpy@mail.gmail.com>
2010-10-28 14:01 ` Santi Béjar
2015-09-09 8:34 ` davilda_
2015-09-09 9:20 ` Jeff King
2015-09-09 16:24 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2007-06-08 10:08 fatal: ambiguous argument 'HEAD': " Thomas Glanzmann
2007-06-08 10:15 ` Junio C Hamano
2007-06-08 10:21 ` Thomas Glanzmann
2007-06-08 10:33 ` Junio C Hamano
2007-06-08 10:38 ` Thomas Glanzmann
2007-06-08 10:27 ` Junio C Hamano
2007-06-10 8:54 ` carbonated beverage
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CC97DC8.1010508@debugon.org \
--to=misfire@debugon.org \
--cc=git@vger.kernel.org \
--cc=ttopwells@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).