Nicolas Pitre <nico@xxxxxxx> writes: > On Tue, 22 Jan 2008, Junio C Hamano wrote: > >> ebiederm@xxxxxxxxxxxx (Eric W. Biederman) writes: >> >> > Random thought. Would it make sense to implement a git paranoid >> > mode to autodetect name mangling. >> > >> > I.e. After opening or creating a file by name we do a readdir in the >> > same directory to make certain we can find that same name/inode >> > combination. Then on name-mangling systems we can autodetect they >> > exist and limit ourselves to just what they don't mangle with no >> > prior knowledge. By refusing to process names that actively >> > get mangled. For small directories that you frequently see in >> > development it shouldn't even be that slow. >> >> Inside init-db where we already check how the filesystem >> behaves, we could have an autodetection. > > I wonder if that is good enough. Git repositories can be copied over to > different filesystems. Do you mean "cp -a"? If I am not mistaken we already have that issue, due to core.filemode, when user does that across filesystems with different behaviours. There is not much we can do against "cp -a" other than telling users that some configurations need to be adjusted. - 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
