From: Karthik Nayak Date: Tue, 03 Nov 2026 10:00:59 GMT Subject: Re: [PATCH v2] check-ref-format: use parse-options API Message-ID: In-Reply-To: "Husain Sitamuwala via GitGitGadget" writes: > From: Hussain Sitamouwala > > The command parses its options by hand, comparing each argument > against string literals. Use the parse-options API instead so that > option handling is consistent with other builtins and the help > output is generated from the option table. > > Keep the existing behavior: --print stays a hidden, deprecated > synonym for --normalize, only --allow-onelevel can be negated, and > parsing stops at the first non-option argument so that options > after are still rejected. > > Drop the early show_usage_if_asked() call, so that -h is handled by > parse_options(). > > Two minor differences come with parse_options(): unambiguous > abbreviations of long options, such as --norm, are accepted, and > "--" may now precede . > If you follow our 'Documentation/SubmittingPatches' guidelines, it states: It is often beneficial to allow some time for reviewers to provide feedback before sending a new version, rather than sending an updated series immediately after receiving a review. This helps collect broader input, gives reviewers in different time zones a fair chance to comment, and avoids unnecessary churn from many rapid iterations. Waiting also encourages you to polish each version before sending it, so reviewers can focus on substantial issues rather than typos or other small mistakes. Seems like Junio's review went unanswered. Which makes it hard for me to consider dedicating time to do another review of the newer version. I would suggest that you engage in the process before sending new versions. I'll hold off reviewing till then :) [snip]