From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Ping Yin" <pkufranky@gmail.com>
Cc: "Charles Bailey" <charles@hashpling.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFC] git reset --recover
Date: Tue, 4 Mar 2008 02:42:13 -0500 [thread overview]
Message-ID: <76718490803032342k18f05d4dte76aacd9292a1233@mail.gmail.com> (raw)
In-Reply-To: <46dff0320803032121v54612b40ke953348e86daf1f@mail.gmail.com>
On Tue, Mar 4, 2008 at 12:21 AM, Ping Yin <pkufranky@gmail.com> wrote:
> On Tue, Mar 4, 2008 at 1:02 AM, Charles Bailey <charles@hashpling.org> wrote:
> >
> > Does 'git fsck' report some dangling blobs? If so (some of) them
> > should be the content of your missing files.
> >
> Good news. So can "--recover" help me find the lost blobs?
git fsck --lost-found. Look under .git/lost-found/other for your blobs.
Anything that's not 41 bytes is a file.
j.
next prev parent reply other threads:[~2008-03-04 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:59 [RFC] git reset --recover Ping Yin
2008-03-03 15:13 ` Santi Béjar
2008-03-03 16:47 ` Ping Yin
2008-03-03 17:02 ` Charles Bailey
2008-03-04 5:21 ` Ping Yin
2008-03-04 7:42 ` Jay Soffian [this message]
2008-03-04 8:22 ` Ping Yin
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=76718490803032342k18f05d4dte76aacd9292a1233@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=pkufranky@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).