git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Patrick Doyle <wpdster@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: How to recover a lost commit...
Date: Thu, 11 Nov 2010 10:50:23 -0600	[thread overview]
Message-ID: <20101111165023.GB16972@burratino> (raw)
In-Reply-To: <AANLkTinfYTMKicr3V=T=scVpOte_XrmaDgVA_oMj2fYU@mail.gmail.com>

Patrick Doyle wrote:

> But I'm curious... given the reflog show below... can any of you tell
> what I did to myself to shoot myself in the foot?  Aside from "use git
> stash next time dummy", is there any way I could have avoided this?

I don't know. :)  But if you still have the svn_to_git_wip branch,
you might want to try

	$ git log -g svn_to_git_wip

which just shows the history of that branch.

> Today I want to pick up where I left off with the work-in-progress (on
> the "svn_to_git_wip" branch).  What I _really_ wanted to do was to
> grab the contents of that branch, dump them into my working directory
> for the master branch, and continue as if nothing had happened.  (This
> is exactly the use case for which git-stash was created, and I
> probably should have used that to begin with.)

Couldn't

	$ git cherry-pick --no-commit svn_to_git_wip
	$ git reset

or something like

	$ git merge --no-commit svn_to_git_wip
	$ git reset

have worked?

Hope that helps,
Jonathan

  parent reply	other threads:[~2010-11-11 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 16:29 How to recover a lost commit Patrick Doyle
2010-11-11 16:49 ` Seth Robertson
2010-11-11 17:34   ` Patrick Doyle
2010-11-11 17:58     ` Jonathan Nieder
2010-11-11 18:19       ` Patrick Doyle
2010-11-11 17:58     ` Junio C Hamano
2010-11-11 16:50 ` Jonathan Nieder [this message]
2010-11-11 17:39   ` Patrick Doyle

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=20101111165023.GB16972@burratino \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=wpdster@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).