Junio C Hamano <gitster@xxxxxxxxx> writes: > So, no. I am not enthused to see this change. A more relevant question to ask you is what the motivation behind this change is. If it is an apparent "inconsistency" that the plumbing command in question takes an explicit command line option but ignores user configuration, then we can stop there---I think we would want to keep it that way. But if it is because "I use this command interactively quite often, and I find it inconvenient because I need to type the long command line option", we may want to step back and understand why you need to run the low level plumbing command in your interactive use case. Perhaps most, but not quite all, of your need, whatever it is, is already satisfied by higher level commands (like "status"?) and what we need is to enrich these end-user facing higher level commands to fill the "gap" to satisfy the need in your use case.
