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

Re: git repository modified after migration

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 11, 2016, 18:19 UTC
Message-ID
<xmqq4mekx9ld.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<5693C48A.7060801@drmicha.warpmail.net>
Michael J Gruber <git@drmicha.warpmail.net> writes:
> This happens whenever the "stat" information changes, e.g. due to
> changed device numbering and such. "git reset --hard" would have been
> the quickiest way to reset the stat cache/index - after git diff, of
> course ;)

That does not quite explain why 'git status' reported modified files in the first place. It would have refreshed the cached stat info in the index as the first thing to do. "git status" I think is the recommended way these days ("update-index --refresh" for us old timers) to nondestructively correct the cached stat information discrepancy caused by "cp -R".

If you need to resort to "reset --hard", then there is something else going on.

Previous: Yang YuNext: Michael J Gruber
Message 4 of 6 in “git repository modified after migration”
  1. Yang YuDec 25, 2015
  2. Michael J GruberJan 11, 2016
  3. Yang YuJan 11, 2016
  4. Junio C HamanoJan 11, 2016
  5. Michael J GruberJan 12, 2016
  6. Junio C HamanoJan 12, 2016

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.