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

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

From
Jeff King <peff@peff.net>
Date
Sep 1, 2011, 21:50 UTC
Message-ID
<20110901215003.GC16308@sigill.intra.peff.net>
In-Reply-To
<vpqmxeoqj61.fsf@bauges.imag.fr>
On Thu, Sep 01, 2011 at 07:14:30PM +0200, Matthieu Moy wrote:
Show 7 quoted lines
> 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.

I wonder if there are racily clean entries[1] in the index, and diff-index reports them as potential changes.

At any rate, filter-branch should probably be refreshing the index before checking for dirtiness, which would give the correct answer either way.

-Peff
[1] See Documentation/technical/racy-git.txt for more information.
Previous: Matthieu MoyNext: Jeff King
Message 3 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.