From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: [PATCH] rev-list: make "struct rev_list_info" static to the only user
Date: Sat, 19 Jul 2025 17:41:04 -0700 [thread overview]
Message-ID: <xmqq4iv71yov.fsf@gitster.g> (raw)
In-Reply-To: <fc4da804-37ed-4425-8dda-14cfcb607906@web.de> ("René Scharfe"'s message of "Sat, 19 Jul 2025 14:36:04 +0200")
René Scharfe <l.s.r@web.de> writes:
>>> * NEEDSWORK: These loops that attempt to find presence of
>>> - * options without understanding that the options they are
>>> + * options without understanding the options they are
>>> * skipping are broken (e.g., it would not know "--grep
>>> * --exclude-promisor-objects" is not triggering
>>> * "--exclude-promisor-objects" option). We really need
>>
>> This tacked-on bit seems funny to me. Isn't the original more correct?
>> The loops do not understand that the options are broken.
>
> No, the options are fine, but the loops are broken -- they cannot tell
> what they are looking at is an option or an argument of a preceding
> option, yet they ignore that latter possibility. So the word "that"
> is best left out.
Or "... understanding the options, which they are skipping, are
broken", perhaps.
> I also don't see a connection to the struct move,
> though.
True, this has nothing to do with the main theme of the patch.
next prev parent reply other threads:[~2025-07-20 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 23:58 [PATCH] rev-list: make "struct rev_list_info" static to the only user Junio C Hamano
2025-07-19 6:35 ` Jeff King
2025-07-19 12:36 ` René Scharfe
2025-07-20 0:04 ` Jeff King
2025-07-20 0:41 ` Junio C Hamano [this message]
2025-07-21 22:46 ` [PATCH] rev-list: update a NEEDSWORK comment Junio C Hamano
2025-07-22 8:16 ` Jeff King
2025-07-22 8:41 ` Kristoffer Haugsbakk
2025-07-22 13:18 ` Junio C Hamano
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=xmqq4iv71yov.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).