Jon Seymour <jon.seymour@xxxxxxxxx> writes: > Ideally, I think we should simply be reporting the log limit exceeded > condition as a fatal condition on its own, and not reporting the > ambiguous ref catch all at all in this case. We have already decided > that the argument is a reference at this point and as such it is not > really ambiguous, it just happens to be out of bounds. A very good point. Would simply replacing that error-then-return-nonzero with a die work? If so we do not even need to worry about new mechanisms to cause different soft error conditions reported back to the caller to be printed. -- 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