From: Jeff King <peff@peff.net>
To: git <git@vger.kernel.org>
Subject: Re: checkout to a reflog entry
Date: Tue, 25 Aug 2009 01:22:01 -0400 [thread overview]
Message-ID: <20090825052200.GA15880@coredump.intra.peff.net> (raw)
In-Reply-To: <20090825045235.GB391@debian.b2j>
On Tue, Aug 25, 2009 at 12:52:35PM +0800, bill lam wrote:
> project(master)$ git checkout master@{1}
> Note: moving to 'master@{1}' which isn't a local branch
> [...]
> It becomes (no branch) although the SHA1 is correct. If I then
> checkout master, then it revert and jump back up the previous master
> HEAD. I tried HEAD@{xx} also failed. What is the correct way of to
> checkout that master@{..} and stay in that master branch? (Sometimes
> it worked I forgot how and why)
A reflog entry is not a branch; it is just a pointer to the commit where
a branch was at some point. Using "git checkout" on it will let you
explore the contents, just as you might with a tag. If you want to build
on it, you need to either:
1. Make a new branch to work on, starting at that point:
git checkout -b my-topic master@{1}
2. Reset your current branch (and worktree) to point at that commit:
git reset --hard master@{1}
-Peff
next prev parent reply other threads:[~2009-08-25 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 4:52 checkout to a reflog entry bill lam
2009-08-25 5:22 ` Jeff King [this message]
2009-08-25 5:37 ` bill lam
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=20090825052200.GA15880@coredump.intra.peff.net \
--to=peff@peff.net \
--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 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).