From: "D. Ben Knoble" <ben.knoble+github@gmail.com>
To: git@vger.kernel.org
Cc: "D. Ben Knoble" <ben.knoble+github@gmail.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: [PATCH 0/5] Fixes for :(optional) path code
Date: Sun, 2 Nov 2025 11:17:43 -0500 [thread overview]
Message-ID: <cover.1762100242.git.ben.knoble+github@gmail.com> (raw)
This series has a few fixes from Phillip's review, set up as individual
patches. Justification is light, as many are hopefully straightforward?
The most important patch comes first. The rest are probably
take-or-leave.
D. Ben Knoble (5):
parseopt: fix :(optional) at command line to only ignore missing files
doc: clarify command equivalence comment
parseopt: use boolean type for a simple flag
config: use boolean type for a simple flag
parseopt: restore const qualifier to parsed filename
Documentation/gitcli.adoc | 2 +-
config.c | 2 +-
parse-options.c | 8 ++++----
3 files changed, 6 insertions(+), 6 deletions(-)
base-commit: a99f379adf116d53eb11957af5bab5214915f91d
--
2.48.1
next reply other threads:[~2025-11-02 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 16:17 D. Ben Knoble [this message]
2025-11-02 16:17 ` [PATCH 1/5] parseopt: fix :(optional) at command line to only ignore missing files D. Ben Knoble
2025-11-04 16:19 ` Phillip Wood
2025-11-04 17:24 ` Junio C Hamano
2025-11-04 17:34 ` Junio C Hamano
2025-11-04 18:24 ` D. Ben Knoble
2025-11-05 16:35 ` Phillip Wood
2025-11-06 17:47 ` Junio C Hamano
2025-11-02 16:17 ` [PATCH 2/5] doc: clarify command equivalence comment D. Ben Knoble
2025-11-02 16:17 ` [PATCH 3/5] parseopt: use boolean type for a simple flag D. Ben Knoble
2025-11-03 5:19 ` Junio C Hamano
2025-11-04 16:21 ` Phillip Wood
2025-11-04 18:22 ` D. Ben Knoble
2025-11-02 16:17 ` [PATCH 4/5] config: " D. Ben Knoble
2025-11-02 16:17 ` [PATCH 5/5] parseopt: restore const qualifier to parsed filename D. Ben Knoble
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=cover.1762100242.git.ben.knoble+github@gmail.com \
--to=ben.knoble+github@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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).