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

Re: reverting back both working copy and commits

From
BBBahadir Balban <bahadir.balban@gmail.com>
Date
Jan 12, 2006, 10:40 UTC
Message-ID
<7ac1e90c0601120240u3f8d7571g5e5bf52b6d3c4c2a@mail.gmail.com>
In-Reply-To
<7vslrutv2h.fsf@assigned-by-dhcp.cox.net>
On 1/11/06, Junio C Hamano <junkio@cox.net> wrote:
Show 8 quoted lines
> Eh?  That should not happen.
>
> Could you elaborate?
> What "git reset --hard" would leave behind are files in the
> working tree that you had when you made the wrongly done commit,
> which were *not* known to git (i.e. you forgot to "git add"
> before committing).  Since they are not known to git, "reset --hard"
> does not touch them.

Sorry, it's my mistake, I later realised the working tree had been updated correctly.

Thanks, Bahadir

Previous: Junio C Hamano
Message 4 of 4 in “reverting back both working copy and commits”
  1. Bahadir BalbanJan 11, 2006
  2. Andreas EricssonJan 11, 2006
  3. Junio C HamanoJan 11, 2006
  4. Bahadir BalbanJan 12, 2006

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.