On Thu, May 6, 2010 at 10:00 PM, Jeff King <peff@xxxxxxxx> wrote: > On Thu, May 06, 2010 at 06:20:34PM -0700, Chris Packham wrote: > >> I noticed a while back that with gitk I kept on getting files shown as >> "Local uncommitted changes, not checked in to index" when I'd made >> modifications to them then backed them out so the working tree content >> was the same as the index. I used to (with git 1.6.x) fix / work >> around this by running git status. >> >> Now, with git 1.7.1, that workaround has stopped working. No doubt > > This was lost in v1.7.0, but should be back in v1.7.2. The actual fix is > 4bb6644 (git status: refresh the index if possible, 2010-04-02). > > You can run "git update-index --refresh" to get the same effect. Running > "git diff" also works. > > There was some talk (and a patch) recently about gitk running > "update-index --refresh", but I don't know if it got picked up. See: > > http://article.gmane.org/gmane.comp.version-control.git/144182 > > -Peff > OK good to know its not just me. I'd add my vote for gitk running "update-index --refresh" in response to a user asking it to refresh, which should satisfy the "gitk doesn't touch anything unless you ask it to" requirement. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html