From: Thomas Rast <trast@student.ethz.ch>
To: Levend Sayar <levendsayar@gmail.com>
Cc: git <git@vger.kernel.org>, Eda Ercan <edaercan@gmail.com>
Subject: Re: panic recovery
Date: Sun, 16 Jan 2011 13:38:54 +0100 [thread overview]
Message-ID: <201101161338.54423.trast@student.ethz.ch> (raw)
In-Reply-To: <AANLkTikBjWU_dm1a+2AQyP-bhdO_WtYJ8OdE7Zs3E=kV@mail.gmail.com>
Levend Sayar wrote:
> git am --abort
>
> After that, we saw that all the sources she developed for two weeks
> are gone.
You can dig up the lost commits from the HEAD reflog after that, which
records all movements of HEAD. See
http://www.kernel.org/pub/software/scm/git/docs/git-reflog.html
The method you described is usually only applicable if you have truly
unreachable objects, which happens e.g. if you lost some content that
was once staged in the index but never committed.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2011-01-16 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 12:33 panic recovery Levend Sayar
2011-01-16 12:38 ` Thomas Rast [this message]
2011-01-16 13:11 ` Thomas Rast
2011-01-17 18:42 ` Junio C Hamano
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=201101161338.54423.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=edaercan@gmail.com \
--cc=git@vger.kernel.org \
--cc=levendsayar@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).