From: Azuama Odinaka Maximus <azuama69@gmail.com>
To: git@vger.kernel.org
Cc: tangajoris@gmail.com, pushkarkumarsingh1970@gmail.com,
gitster@pobox.com, christian.couder@gmail.com,
Azuama Odinaka Maximus <azuama69@gmail.com>
Subject: [RFC PATCH 0/2] parse-options: improve early option scanning
Date: Tue, 10 Nov 2026 17:13:11 +0100 [thread overview]
Message-ID: <20261110161314.35213-1-azuama69@gmail.com> (raw)
This RFC series shares my progress on improving early option
scanning in rev-list and exploring a reusable scanning API.
The first patch updates rev-list's early scan to account for
options that consume arguments.
The second patch introduces a generic early option-scanning API
with tests, as a step towards a more reusable solution.
The rev-list patch still uses an initial hardcoded option list,
which I recognise is fragile based on the review feedback.
I am investigating how to avoid this limitation and how best
to integrate revision-option argument parsing without triggering
unwanted parsing side effects.
I would appreciate feedback on the direction of this work,
particularly the API design and its integration with revision
option parsing.
Signed-off-by: Azuama Odinaka Maximus <azuama69@gmail.com>
Azuama Odinaka Maximus (2):
rev-list: handle arguments in early option scan
parse-options: add early option scanning
builtin/rev-list.c | 55 +++++++-
parse-options.c | 249 ++++++++++++++++++++++++++++++----
parse-options.h | 22 +++
t/helper/test-parse-options.c | 236 ++++++++++++++++++++++++++++++++
t/t0040-parse-options.sh | 6 +
t/t6022-rev-list-missing.sh | 26 ++++
6 files changed, 562 insertions(+), 32 deletions(-)
--
2.53.0
next reply other threads:[~2026-11-10 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 16:13 Azuama Odinaka Maximus [this message]
2026-11-10 16:13 ` [RFC PATCH 1/2] rev-list: handle arguments in early option scan Azuama Odinaka Maximus
2026-11-10 16:13 ` [RFC PATCH 2/2] parse-options: add early option scanning Azuama Odinaka Maximus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261110161314.35213-1-azuama69@gmail.com \
--to=azuama69@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pushkarkumarsingh1970@gmail.com \
--cc=tangajoris@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox