git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Reverting to old commit

From
SRSverre Rabbelier <alturin@gmail.com>
Date
May 27, 2008, 19:32 UTC
Message-ID
<bd6139dc0805271232x53e91c0fx699c1ea0769e50ec@mail.gmail.com>
In-Reply-To
<8345bd80805271050q7412917bt292a276fbbe6aed3@mail.gmail.com>
On Tue, May 27, 2008 at 7:50 PM, Marcus <prima@wordit.com> wrote:
Show 8 quoted lines
> 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?

Have a look at the reflog (git reflog) perhaps combined with "git log -p" which will show the changes each commit introduced as well.

-- 
Cheers,

Sverre Rabbelier
Previous: Sverre RabbelierNext: Dirk Süsserott
Message 5 of 8 in “Reverting to old commit”
  1. MarcusMay 27, 2008
  2. Jakub NarebskiMay 27, 2008
  3. Brandon CaseyMay 27, 2008
  4. Sverre RabbelierMay 27, 2008
  5. Sverre RabbelierMay 27, 2008
  6. Dirk SüsserottMay 27, 2008
  7. Paolo BonziniMay 27, 2008
  8. Robin RosenbergMay 27, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.