git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Marcus <prima@wordit.com>
Cc: git@vger.kernel.org
Subject: Re: Reverting to old commit
Date: Tue, 27 May 2008 22:02:45 +0200	[thread overview]
Message-ID: <483C68E5.1040408@dirk.my1.cc> (raw)
In-Reply-To: <8345bd80805271050q7412917bt292a276fbbe6aed3@mail.gmail.com>

Marcus schrieb:
> Newbie question: What's the simplest way to find an old commit and revert?
>
> Say you have a version from yesterday which worked and today's
> experiments failed, so you want to go back to that working version.
> Unfortunately, it's not tagged. Instead you need to actually view the
> code to identify the version you want. I thought maybe gitk might
> help, but I can't find my way with gitk. I hoped you could browse
> revisions easier in a GUI and tell gitk or git-gui to revert?
>
> Thanks,
>
> Marcus
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   
Probably I misunderstood, but: do you *know* which version worked
well? I.e. when you start gitk, can you point to the working
commit and are just wondering how to revert to that one?

Then gitk's "reset ... branch to here" could help you. Right-click
the desired commit and reset the branch.

There's no need to have a tag for this. You can even create a
tag afterwards for any commit you like. It's just an alias for
the commit id (sha1).

If you cannot identify the working commit, then please forget
my answer and follow the "git bisect" proposals.

  parent reply	other threads:[~2008-05-27 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 17:50 Reverting to old commit Marcus
2008-05-27 18:09 ` Jakub Narebski
2008-05-27 20:43   ` Brandon Casey
2008-05-27 23:00     ` Sverre Rabbelier
2008-05-27 19:32 ` Sverre Rabbelier
2008-05-27 20:02 ` Dirk Süsserott [this message]
2008-05-27 20:17   ` Paolo Bonzini
2008-05-27 20:41 ` Robin Rosenberg

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=483C68E5.1040408@dirk.my1.cc \
    --to=newsletter@dirk.my1.cc \
    --cc=git@vger.kernel.org \
    --cc=prima@wordit.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).