Glen Choo <chooglen@xxxxxxxxxx> writes: > Ah, I meant that this bug occurred because most users of config use > git_config()/repo_config() (a wrapper around config sets), so it's very > easy to accidentally read repo config, e.g. in the middle of parsing > config (config file -> config set). I'd imagine it might also be quite > easy to read repo config while reading repo config (config set -> config > set), which would make current_config_* return the wrong thing, but at > least it doesn't BUG(). I think BUG() is better than silently computing a wrong result, but it would probably be much rare than the problem at hand, and with the getting rid of global dependencies, it won't be an issue anymore, hopefull? So it is good. > The "reverse" case (config set -> config file) is very _unlikely_ > because very few places need to know about config files, so it's > unlikely that we'd have an explicit call to parse a config file, > especially in the middle of reading repo config. As long as existing codepaths do not do that, it would be OK ;-) Thanks.
