On Tue, Dec 9, 2014 at 5:04 PM, brian m. carlson <sandals@xxxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Dec 08, 2014 at 09:05:07PM +0700, Nguyễn Thái Ngọc Duy wrote: >> If the user enables untracked cache, then >> >> - move worktree to an unsupported filesystem >> - or simply upgrade OS >> - or move the whole (portable) disk from one machine to another >> - or access a shared fs from another machine >> >> there's no guarantee that untracked cache can still function properly. >> Record the worktree location and OS footprint in the cache. If it >> changes, err on the safe side and disable the cache. The user can >> 'update-index --untracked-cache' again to make sure all conditions are >> met. > > My use case for untracked cache is where I have one machine with a > repository and which is also mounted via sshfs on another machine. It > looks like this will disable the cache every time I change the machine I > access it on. Would you be willing to accept a patch for a configuration > option to disable this? Torsten also does not like this patch. Maybe I'm just too paranoid. Maybe we can drop this patch. -- Duy -- 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