From: Sverre Rabbelier <srabbelier@gmail.com>
To: jake varghese <jake@orgsync.com>
Cc: git@vger.kernel.org
Subject: Re: Git screwup with reset
Date: Mon, 18 May 2009 17:11:38 +0200 [thread overview]
Message-ID: <fabb9a1e0905180811r6e408ce5ged65ddfb3846111c@mail.gmail.com> (raw)
In-Reply-To: <9D569322-6A7B-4447-962C-0C740945E227@orgsync.com>
Heya,
On Mon, May 18, 2009 at 16:58, jake varghese <jake@orgsync.com> wrote:
> Anyone know of a way to get this stuff back.
Make a backup copy of that .git directory, so that whatever you do you
won't lose that work ;). Also, the reason you can't merge or rebase
that hash is because it's the hash of a tree or a blob, not a commit.
You can use git commit-tree [0] to create a commit from your lost
tree, but that works only if you have a tree (for just a blob you can
use git cat-file [1])
[0] http://www.kernel.org/pub/software/scm/git/docs/git-commit-tree.html
[1] http://kernel.org/pub/software/scm/git/docs/git-cat-file.html
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-05-18 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 14:58 Git screwup with reset jake varghese
2009-05-18 15:08 ` Shawn O. Pearce
2009-05-18 15:11 ` Sverre Rabbelier [this message]
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=fabb9a1e0905180811r6e408ce5ged65ddfb3846111c@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=jake@orgsync.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).