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

Re: Some information that git diff saves and that git status does not

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Mar 9, 2010, 06:35 UTC
Message-ID
<4B95EC43.2040705@viscovery.net>
In-Reply-To
<7vpr3emr3s.fsf@alter.siamese.dyndns.org>
Junio C Hamano schrieb:
> I didn't fully read what you wrote but after you copy a repository from
> one to another outside git (be it done with unison or rsync), you should
> run "update-index --refresh".

And the reason for this is that git also looks at the inode numbers, and I guess that unison does not go as far as to preserve them between machines...

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “Some information that git diff saves and that git status does not”
  1. SergioMar 8, 2010
  2. Junio C HamanoMar 8, 2010
  3. Johannes SixtMar 9, 2010
  4. Junio C HamanoMar 9, 2010
  5. Sergio CallegariMar 9, 2010
  6. Dmitry PotapovMar 9, 2010
  7. Jens LehmannMar 8, 2010

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.