From: Eric Raible <raible@gmail.com>
To: git@vger.kernel.org
Subject: Re: RFC: perhaps a "new file" should not be deleted by "git reset --hard"
Date: Thu, 11 Sep 2008 20:26:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20080911T202202-144@post.gmane.org> (raw)
In-Reply-To: 20080911061454.GA8167@glandium.org
Mike Hommey <mh <at> glandium.org> writes:
> Note that reflog only contains references to commit sha1s, so it can't
> track index status.
Yes I realize that.
My point was that the file is entirely gone (except via "git fsck").
I wouldn't expect the reflog to reference it, but I was just mentioning
it for completeness (since it's often help in recovering from types of
lossage).
prev parent reply other threads:[~2008-09-11 20:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 19:12 RFC: perhaps a "new file" should not be deleted by "git reset --hard" Eric Raible
[not found] ` <eafc0afe0809101912v72916d3hce9ae5d6812f0db8@mail.gmail.com>
2008-09-11 2:14 ` Changsheng Jiang
2008-09-11 2:38 ` Elijah Newren
2008-09-11 20:50 ` Eric Raible
2008-09-11 21:34 ` Junio C Hamano
2008-09-11 22:19 ` Eric Raible
2008-09-11 23:04 ` Jeff Whiteside
2008-09-11 23:29 ` Eric Raible
2008-09-11 2:46 ` Eric Raible
2008-09-11 6:05 ` Changsheng Jiang
2008-09-11 6:15 ` RFC: perhaps a Eric Raible
2008-09-11 16:32 ` RFC: perhaps a "new file" should not be deleted by "git reset --hard" Elijah Newren
[not found] ` <3ab397d0809111022m24c81bd9y2520f6be478babd3@mail.gmail.com>
2008-09-11 21:24 ` Eric Raible
2008-09-11 23:39 ` Miklos Vajna
2008-09-11 23:49 ` Eric Raible
2008-09-12 15:41 ` Miklos Vajna
2008-09-11 6:14 ` Mike Hommey
2008-09-11 20:26 ` Eric Raible [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=loom.20080911T202202-144@post.gmane.org \
--to=raible@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.