On Thu, May 20, 2010 at 8:01 PM, Andy Parkins <andyparkins@xxxxxxxxx> wrote: > On Thursday 20 May 2010 18:49:41 Jens Lehmann wrote: >> Am 20.05.2010 19:45, schrieb Andy Parkins: >> > (Most of my >> > personal use of submodule is embedding large projects that I want to be >> > able to guarantee are at a particular version, but I don't really >> > change them) >> >> But to guarantee they are at a particular version they have to be checked >> for local modifications (no matter if they happened accidentally or on >> purpose), no? > > A valid point. > > Surely though in my own .git/config I can be allowed to tell git that I > don't care about that risk? > > I've got a top level module that used to diff/status instantly; now git > scans an entire Linux kernel checkout and an entire ffmpeg checkout. > Painful. I fully accept that it was my own choice to arrange my repository > in this way, but in my defence, it was fine last week :-) Sounds similar to the old "slow lstat" stuff. How about setting assume-unchanged bit on submodules? I don't know if it works. If it does not, maybe we could reuse the bit to ignore changes in submodules. -- 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