Duy Nguyen <pclouds@xxxxxxxxx> writes: > I have a better plan: stop exposing parse-options loop to outside. > What all these commands need is the ability to deal with unknown > options (or non-options in update-index case). They could register > callbacks to deal with those and keep calling parse_options() instead. > I'm converting rev-list to use parse_options() and as an intermediate > step, this callback idea should work well. The end game though is a > single parse_options() call that covers everything in, say, git-log. > But we will see. Sounds like a good plan. Thanks.
