Jeff King <peff@xxxxxxxx> writes: > Right, that is the "gotcha" I mentioned in my other email. Though that > is the way it has behaved historically, my argument is that users are > unreasonable to expect it to work: > > 1. It is not consistent with the rest of Git commands. > > 2. It is inconsistent with respect to existing options (and is an > accident waiting to happen when new options are added). > > So I'd consider it a bug-fix. So the counter-proposal here is just to drop KEEP_UNKNOWN_OPT and deliberately break them^W^W^Wrealign their expectations? I do not have much stake in sparse-checkout, so I am fine with that direction. But I suspect other folks on the list would have users of their own who would rather loudly complain to them if we broke them ;-) I'll see how bad the fallout would be if we go that route, using the test modification I made for the previous rounds as yardsticks. Thanks.
