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

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 9, 2010, 06:56 UTC
Message-ID: <7vmxyi0yqk.fsf@alter.siamese.dyndns.org>
In-Reply-To: <4B95EC43.2040705@viscovery.net>

Johannes Sixt <j.sixt@viscovery.net> writes:

Show 7 quoted lines

> 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...

True; we used to (and you can still configure git to) check st_dev too but we stopped to doing that by default as it is unstable even in a normal use case (read: no "cp" involved) on some networked file systems.

I wonder how stable inum is on inode-less filesystems (say FAT). I guess it is not usually a problem because carrying repositories on USB keychains is typically done as a sneakernet and with bare repositories.