From: Junio C Hamano <junkio@cox.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Bill Lear <rael@zopyra.com>, git@vger.kernel.org
Subject: Re: Stupid question on getting branch from yesterday
Date: Wed, 14 Feb 2007 11:54:06 -0800 [thread overview]
Message-ID: <7v7iuko6qp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070214194919.GE28290@spearce.org> (Shawn O. Pearce's message of "Wed, 14 Feb 2007 14:49:19 -0500")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> Bill Lear <rael@zopyra.com> wrote:
>> I have not yet figured this one out: I have not tagged anything, but
>> know that I checked in something lame sometime between now and two days
>> ago. How do I get my working repo to be that as it was, say, yesterday?
>>
>> Do I do:
>>
>> % git log --since="2 days ago"
>>
>> parse, the output for the commit I want, and then do
>>
>> % git reset <SHA>
>
> No. This would update your branch and your index to <SHA>, but
> leave your working directory alone. That's not what you want here.
>
> Use `git checkout <SHA>` which will detach your HEAD and seek to
> the commit, leaving your current commit alone. Later you can get
> back by `git checkout oldbranch`.
Ah, I thought Bill was talking about getting rid of lame one,
but now when I re-read his message, I think he is talking about
going there to take a look, not necessarily wanting to discard
or alter history.
Sorry, Bill, if that is the case, forget what I said about
reset/revert/rebase in the other message.
next prev parent reply other threads:[~2007-02-14 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:38 Stupid question on getting branch from yesterday Bill Lear
2007-02-14 19:49 ` Shawn O. Pearce
2007-02-14 19:54 ` Junio C Hamano [this message]
2007-02-14 20:24 ` Bill Lear
2007-02-14 20:28 ` Bill Lear
2007-02-14 20:36 ` Jeff King
2007-02-14 19:50 ` Junio C Hamano
2007-02-14 21:13 ` Linus Torvalds
2007-02-14 21:25 ` Junio C Hamano
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=7v7iuko6qp.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.com \
--cc=spearce@spearce.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