From: Junio C Hamano <gitster@pobox.com>
To: Azuama Odinaka Maximus <azuama69@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] rev-list: skip --grep argument in early scan
Date: Fri, 23 Oct 2026 11:14:27 -0700 [thread overview]
Message-ID: <xmqqzew45loc.fsf@gitster.g> (raw)
In-Reply-To: <20261021172458.6373-1-azuama69@gmail.com> (Azuama Odinaka Maximus's message of "Wed, 21 Oct 2026 18:24:57 +0100")
Azuama Odinaka Maximus <azuama69@gmail.com> writes:
> +test_expect_success "--grep accepts a pattern beginning with --" '
> + git rev-list --grep=--missing-only --max-count=1 HEAD >expect &&
> + git rev-list --grep --missing-only --max-count=1 HEAD >actual &&
> + test_cmp expect actual
> +'
> +test_expect_success "--grep does not trigger --exclude-promisor-objects in early scan" '
> + git rev-list --grep=--exclude-promisor-objects --missing=print HEAD >expect &&
> + git rev-list --grep --exclude-promisor-objects --missing=print HEAD >actual &&
> + test_cmp expect actual
> +'
Have a blank line between tests.
Do these tests truly verify anything beyond "the command line parser
is not broken by my commit"? There is nothing in the history that
would trigger '--missing-only'; there is no positive indication that
the pattern starting with "--" was used by '--grep' at all. The only
clue that '--missing-only' was not taken as a command line option is
that the command did not fail due to a lack of '--missing=<how>'.
The same issue exists in the second added test.
Thanks.
next prev parent reply other threads:[~2026-10-23 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 15:12 [PATCH] rev-list: skip --grep argument in early scan Azuama Odinaka Maximus
2026-10-21 15:42 ` Pushkar Singh
2026-10-21 17:24 ` [PATCH v2] " Azuama Odinaka Maximus
2026-10-22 13:45 ` Pushkar Singh
2026-10-23 18:14 ` Junio C Hamano [this message]
2026-10-26 8:30 ` [PATCH v3] " 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=xmqqzew45loc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=azuama69@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.