neat! this also worked great
On Wed, Oct 9, 2013 at 4:21 PM, Dale R. Worley <wor...@alum.mit.edu> wrote:
> > > 1. Copy (resursively) the whole project directory to some other place,
> > > right now. This is not to inflict more harm than already done.
> > > Git won't delete anything irreversibly, but "drastic" operations
> > > like the one you supposedly did leave some objects as "unreachable"
> > > (in Git's parlance, they are now "dangling"). They will be there
> > > until a garbage collection is run on the repository, which is
> > > an automated operation, so, again, stop doing anything there and
> > > copy over the whole project directory.
> If you staged your changes, then they were stored in the repository as
> objects. Once you reset the index, references to the changed file
> contents were lost, but until Git garbage collects, the objects are
> still there. "git fsck --unreachable" lists all objects that can't be
> reached, so changed file contents that were staged should be
> discoverable that way. You can dump the contents of an individual
> file with "git cat-file <hash>".
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.