Jeff King <peff@xxxxxxxx> writes: > "find the highest limit needed and report once" strategy you used above? Wasn't "find the highest limit" your invention in merge-recursive? The only deliberate fix in merge-recursive codepath on top of what you did is to allow squelching the warning when verbosity is set to more quiet than the default, and removal of the "set var to this value" advice when the value we are going to suggest is too high already and will not help. As to the warnings in "log" output, I actually prefer leaving saved_* out and showing the warning per internal diff invocation. My initial iteration was indeed coded that way, and I did the "find the highest" only to mimic what was already in merge-recursive. -- 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