On Fri, Dec 20, 2019 at 9:37 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > I do not think origin and scope are orghogonal, though. Can the > same file appear as the source for different configuration var-value > pair in two different scopes? I meant orthogonal in two senses: That given the current implementation you don't need to have both options active at the same time but can have them active at both times. And that origin and scope correlate, but aren't necessarily one-for-one. For example, --show-origin lists in a known order, but it follows includes and lists the origin as the included file. so if you include a file globally which has includeif "gitdir:..." directives then it can get hairy when all your config files are structured like that. Although, to be fair I doubt that that kind of situation is normal > > It is likely that you can _guess_ with high precision that given a > pathname reported by --show-origin what scope it is in. It on the > other hand is not so trivial given a scope to guess which exact file > a var-value pair came from, I would think.\ Normally yes, but things can get complicating depending on your configuration/include situation.
