Git development
 help / color / mirror / Atom feed
From: Bill Lear <rael@zopyra.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Stupid question on getting branch from yesterday
Date: Wed, 14 Feb 2007 14:24:09 -0600	[thread overview]
Message-ID: <17875.28649.796301.17874@lisa.zopyra.com> (raw)
In-Reply-To: <20070214194919.GE28290@spearce.org>

On Wednesday, February 14, 2007 at 14:49:19 (-0500) Shawn O. Pearce 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, ok, then, you can use checkout with the SHA...

Junio, I was talking about just getting back to "lame" and inspecting,
fixing, etc., not getting rid of things back to then.


Bill

  parent reply	other threads:[~2007-02-14 20:24 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
2007-02-14 20:24   ` Bill Lear [this message]
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=17875.28649.796301.17874@lisa.zopyra.com \
    --to=rael@zopyra.com \
    --cc=junkio@cox.net \
    --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