I would suggest displaying a warning in case of invalid input (such as this out of range error), and to fall back to output all as if the "-n" flag was unspecified. If more strict handling is still desired, it could instead be a deprecation warning with a grace period, giving applications some time to update their git usage. On Wed, Feb 21, 2024 at 9:25 PM Sean Allred <allred.sean@xxxxxxxxx> wrote: > > > Maarten Ackermans <maarten.ackermans@xxxxxxxxx> writes: > > Applications that have been relying on undocumented features and > > limits since they were introduced, now face a hard crash: "fatal: > > '9007199254740991': not an integer". Regardless of whether this is an > > improvement for future implementations, a crash in existing ones is a > > suboptimal experience at the least. > > What behavior would you propose instead? > > -- > Sean Allred
