From: Junio C Hamano <gitster@pobox.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, derrickstolee@github.com
Subject: Re: [PATCH 0/2] builtin/show-ref.c: support `--count` for limiting output
Date: Mon, 06 Jun 2022 15:52:19 -0700 [thread overview]
Message-ID: <xmqqo7z54d7g.fsf@gitster.g> (raw)
In-Reply-To: <cover.1654552560.git.me@ttaylorr.com> (Taylor Blau's message of "Mon, 6 Jun 2022 17:56:01 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> This short patch series adds support for a new `--count` argument for limiting
> the output of `show-ref` (à-la the `for-each-ref` option by the same name).
It makes me wonder why we limit this to show-ref.
$ git --pipe-to-head-N=3 any-command args...
IOW, having to add an option like this feels absurd.
> This is useful in contexts where a caller wants to avoid enumerating more
> references than necessary (e.g., they only care whether a tag exists, but not
> how many or what they are called) but doesn't have control of the output stream
> (e.g., they are in Ruby and can't pipe the output to `head -n 1`).
Are you saying that Ruby is incapable of run a command line like
av[0] = "sh"
av[1] = "-c"
av[2] = "git show-ref blah | head -n 1"
av[3] = NULL
?
next prev parent reply other threads:[~2022-06-06 22:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 21:56 [PATCH 0/2] builtin/show-ref.c: support `--count` for limiting output Taylor Blau
2022-06-06 21:56 ` [PATCH 1/2] builtin/show-ref.c: rename `found_match` to `matches_nr` Taylor Blau
2022-06-06 21:56 ` [PATCH 2/2] builtin/show-ref.c: limit output with `--count` Taylor Blau
2022-06-06 23:09 ` Junio C Hamano
2022-06-07 8:07 ` Ævar Arnfjörð Bjarmason
2022-06-07 21:13 ` Taylor Blau
2022-06-07 21:31 ` Ævar Arnfjörð Bjarmason
2022-06-08 16:10 ` Junio C Hamano
2022-06-06 22:52 ` Junio C Hamano [this message]
2022-06-06 22:57 ` [PATCH 0/2] builtin/show-ref.c: support `--count` for limiting output Taylor Blau
2022-06-06 23:00 ` Junio C Hamano
2022-06-07 19:41 ` Derrick Stolee
2022-06-07 8:18 ` Ævar Arnfjörð Bjarmason
2022-06-07 21:04 ` Taylor Blau
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=xmqqo7z54d7g.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.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 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.