On Wed, 9 Oct 2013 10:40:36 -0700 (PDT)
Garrett Fritz <garrettfr...@gmail.com> wrote:
> well no other place has the changes I made that were reset...
> On Wednesday, October 9, 2013 11:38:12 AM UTC-6, Dale Worley wrote:
> > >
> > > Any way to 'undo' this reset changes? None of them were
> > > committed obviously so scary time.
> > Do you have backups?
> > In the long run, you should use a tool that requires confirmation
> > of such a drastic action.
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 usually
an automated operation, so, again, stop doing anything there and
copy over the whole project directory.
2. Here, we discuss Git, not GitExtensions, so, for instance, I have no
idea what this operation really does (a fun thing is that I recommend
newcomers this front end as I was pleased by it when I evaluated
various GUI front-ends to Git, but I don't use any of them myself).
So the next step is to go to the support list of that project and
ask for help there. Ask them to explain what has happened *in Git's
terms* and if there a way to recover using their tool -- specifically
ask if operations on "the reflog" are supported because the reflog
is a special place where each "drastic" movements of branches' heads
are recorded so changes are very high you still have a reference to
the now lost tip commit of the affected branch.
If they won't help, return there and we'll discuss how to use reflog
using no more than plain Git tools.
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.