[RFC] git reset --recover

> Today i use git reset carelessly and lose all my changes!
>
>  To remind other people not do the same wrong thing, i share my
>  experience and propose a new option to avoid this happens again.
>  ------------------------------------
>  foo
>    .git
>     bar
>         file1
>         file2
>  ------------------------------------
>
>  In the direcotry structure above, i want to make bar as a repository
>  (which hasn't yet been tracked by foo repository). I should have done
>  this as follows
>
>  -------------------------------------------
>  cd bar
>  git init
>  git add
>  ------------------------------------------
>
>  but i fogot to type "git init" which results that file1 and file2 are
>  added to index of foo repository. I tried to revert the operation
>  using "git reset". And the tragedy happened at that time because i
>  made so fatal  a mistake that i typed "git reset --hard". And i lost
>  all my files in bar dir!

>  >
>  >  but i fogot to type "git init" which results that file1 and file2 are
>  >  added to index of foo repository. I tried to revert the operation
>  >  using "git reset". And the tragedy happened at that time because i
>  >  made so fatal  a mistake that i typed "git reset --hard". And i lost
>  >  all my files in bar dir!
>
>  "git reset" was sufficient.
>

>
>  >
>  >  So, can we introduce a --recover option for "git reset" to save the
>  >  foolish or careless people like me?
>
>  Another possibility would be to not delete a file that is absent in
>  both the old and new HEAD, even if it was in the index.
>

> 
> but i fogot to type "git init" which results that file1 and file2 are
> added to index of foo repository. I tried to revert the operation
> using "git reset". And the tragedy happened at that time because i
> made so fatal  a mistake that i typed "git reset --hard". And i lost
> all my files in bar dir!

> On Mon, Mar 03, 2008 at 10:59:14PM +0800, Ping Yin wrote:
>  >
>
>  If they've been added to the index then the objects should be in your
>  git repository, it's just that it may be hard to find them.
>
>  Does 'git fsck' report some dangling blobs?  If so (some of) them
>  should be the content of your missing files.
>

> 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?

> 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.
>