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 16:00:00 -0700 [thread overview]
Message-ID: <xmqqk09t4cun.fsf@gitster.g> (raw)
In-Reply-To: <Yp6GRccc5UElNrZb@nand.local> (Taylor Blau's message of "Mon, 6 Jun 2022 18:57:09 -0400")
Taylor Blau <me@ttaylorr.com> writes:
> If you're strongly opposed to having `show-ref` match `for-each-ref`'s
> `--count` option, I won't be too sad. But I'm not in a huge rush to
> replace this series with `git --pipe-to-head-N=<n>` either, FWIW.
Heh, to me "git --pipe-to-head-N=<n>" smells equally absurd, too ;-)
next prev parent reply other threads:[~2022-06-06 23:00 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 ` [PATCH 0/2] builtin/show-ref.c: support `--count` for limiting output Junio C Hamano
2022-06-06 22:57 ` Taylor Blau
2022-06-06 23:00 ` Junio C Hamano [this message]
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=xmqqk09t4cun.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 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).