From: Patrick Steinhardt <ps@pks.im>
To: git@vger.kernel.org
Subject: [PATCH 0/3] revision: handle pseudo-opts in `--stdin` mode
Date: Wed, 14 Jun 2023 14:18:28 +0200 [thread overview]
Message-ID: <cover.1686744685.git.ps@pks.im> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi,
both git-rev-list(1) and git-log(1) provide a `--stdin` mode that will
cause these commands to read additional commits from standard input. The
primary usecase will typically be scripts that potentially process a
long list of commits which might otherwise bust command line length
limits.
One notable omission though is that this mode does not allow us to pass
pseudo-options like `--all`, `--branch`, `--glob=` or `--not`. And while
it is possible to mix command line arguments and `--stdin` in order to
mix both pseudo-options and a potentially large set of commits, the end
result is arguably more complex for the user.
This patch series thus implements support for handling pseudo-options in
`--stdin` mode for both git-rev-list(1) and git-log(1).
Patrick
Patrick Steinhardt (3):
revision: reorder `read_revisions_from_stdin()`
revision: small readability improvement for reading from stdin
revision: handle pseudo-opts in `--stdin` mode
Documentation/rev-list-options.txt | 9 ++--
revision.c | 76 +++++++++++++++++-------------
t/t6017-rev-list-stdin.sh | 32 +++++++++++++
3 files changed, 79 insertions(+), 38 deletions(-)
--
2.41.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-06-14 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 12:18 Patrick Steinhardt [this message]
2023-06-14 12:18 ` [PATCH 1/3] revision: reorder `read_revisions_from_stdin()` Patrick Steinhardt
2023-06-14 16:01 ` Junio C Hamano
2023-06-14 12:18 ` [PATCH 2/3] revision: small readability improvement for reading from stdin Patrick Steinhardt
2023-06-14 16:03 ` Junio C Hamano
2023-06-14 12:18 ` [PATCH 3/3] revision: handle pseudo-opts in `--stdin` mode Patrick Steinhardt
2023-06-14 15:56 ` Junio C Hamano
2023-06-15 14:25 ` Patrick Steinhardt
2023-06-15 14:39 ` [PATCH v2 0/3] " Patrick Steinhardt
2023-06-15 14:39 ` [PATCH v2 1/3] revision: reorder `read_revisions_from_stdin()` Patrick Steinhardt
2023-06-15 14:39 ` [PATCH v2 2/3] revision: small readability improvement for reading from stdin Patrick Steinhardt
2023-06-15 14:39 ` [PATCH v2 3/3] revision: handle pseudo-opts in `--stdin` mode Patrick Steinhardt
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.1686744685.git.ps@pks.im \
--to=ps@pks.im \
--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 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).