Matheus Tavares Bernardino <matheus.bernardino@xxxxxx> writes: > Hmm, I may have gotten a little confused here. Are you talking > about the attributes stack (which contains .gitattributes and > info/attributes)? If so, isn't this stack already rebuild for > every path? I mean, by the previous call chain it seems to me that > at least these two files are reread for every path. Yes, but for the switch that happens when coming out of a normal directory and then descending into another normal directory is just to pop the entries from the directory hierarchy we are getting out of, and then pushing the entries from the new directory hierarchy. We would not be discarding and rereading $GIT_DIR/info/ or the .gitattribute file from the top-level of the working tree. Descending into a submodule is fundamentally and completely different. None of the attributes defined in the superproject should affect the paths in the submodule, as it is a totally separate project, oblivious to the existence of enclosing the superproject. Every time we look up attributes for a path in a project (either the superproject or a submodule) that is different from the one we did a look-up the last time, we'd not just need to pop a handful and push a handful, but need to rebuild the stack completely from scratch, no?
