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

Re: Cannot rewrite branch(es) with a dirty working directory

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Sep 1, 2011, 17:14 UTC
Message-ID
<vpqmxeoqj61.fsf@bauges.imag.fr>
In-Reply-To
<CACyv8dfL-G0Px0aFe3VFNHP-1xRUDLsFxgUu3amPGzO7qKp7jQ@mail.gmail.com>
James Blackburn <jamesblackburn@gmail.com> writes:
> Is there a particular reason why filter-branch thinks the tree is
> dirty,

No idea. It comes after a "git reset --hard", so it's supposed to be clean.

> and status magically fixes this?

The index is considered dirty if the stat information (timestamp) is different. "git status" updates the stat-cache to consider unmodified content as up-to-date. So, it's normal that a "git status" repairs the dirty index.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: James BlackburnNext: Jeff King
Message 2 of 5 in “Cannot rewrite branch(es) with a dirty working directory”
  1. James BlackburnSep 1, 2011
  2. Matthieu MoySep 1, 2011
  3. Jeff KingSep 1, 2011
  4. Jeff KingSep 1, 2011
  5. Matthieu MoySep 2, 2011

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.