From: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
Date: Sun, 22 May 2005 12:28:49 GMT
Subject: running git-update-cache --refresh on different machines on a NFS share always ends up in a lot of io/cpu/time waste
Message-ID: <20050522122849.GJ15178@cip.informatik.uni-erlangen.de>

Hello,
I wonder why 'git-update-cache --refresh' running in the same directory
shared via NFS ends up in reindexing the whole files when running on
different machines on a NFS share.

Is there a reason for this or can it easily be fixes. I also wonder if
the locking which is used to lock the cache is 'nfs safe'.

	Thomas