Jeff King <p...@peff.net> writes: > So not too bad (and you could probably refactor it to avoid some of the > duplication). Though it does get some obscure cases wrong, like: > > git merge --continue --verbose --quiet > > I dunno. Maybe I am leading you down a rabbit hole, and we should just > live with silently ignoring useless options.
I think you need to handle this in parse-options API if you really wanted to do this correctly. <xmqq60mn671x....@gitster.mtv.corp.google.com> may serve as a reasonable outline for building one.
