From: Jeff King <peff@peff•net>
To: Aaron Plattner <aplattner@nvidia•com>
Cc: Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org, Patrick Steinhardt <ps@pks•im>,
Rahul Rameshbabu <rrameshbabu@nvidia•com>,
Lucas De Marchi <demarchi@kernel•org>
Subject: Re: [PATCH v2] remote-curl: Use auth for probe_rpc() requests too
Date: Tue, 13 Jan 2026 21:20:57 -0500 [thread overview]
Message-ID: <20260114022057.GA858110@coredump.intra.peff.net> (raw)
In-Reply-To: <a919f4cf-8355-43dd-a552-df99325e4cc6@nvidia.com>
On Tue, Jan 13, 2026 at 05:06:20PM -0800, Aaron Plattner wrote:
> > Hopefully, $(test_seq 2000) would not bust $(sysconf ARG_MAX), which
> > could be as low as 4KB, on any system we care about. If not, of
> > course we could
> >
> > test_seq 2000 |
> > xargs printf "create ...\n" |
> > git update-ref --stdin
> >
> > which probably is not all that more expensive than what you wrote above.
>
> That's a good call. I tried this
>
> test_seq 2000 |
> xargs printf "create refs/heads/branch-%d @\n" |
> git update-ref --stdin
>
> and verified it produces the same results, as does the same plus passing "-n
> 10" to xargs.
test_seq can take a format parameter these days, so just:
test_seq -f "create refs/heads/branch-%d @" |
git update-ref --stdin
is enough, and saves some processes.
-Peff
next prev parent reply other threads:[~2026-01-14 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 3:19 [PATCH v2] remote-curl: Use auth for probe_rpc() requests too Aaron Plattner
2026-01-13 6:49 ` Patrick Steinhardt
2026-01-13 13:09 ` Junio C Hamano
2026-01-14 1:06 ` Aaron Plattner
2026-01-14 2:20 ` Jeff King [this message]
2026-01-14 14:11 ` Junio C Hamano
2026-01-14 16:33 ` Aaron Plattner
2026-01-14 17:30 ` Jeff King
2026-01-14 17:41 ` 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=20260114022057.GA858110@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=aplattner@nvidia$(echo .)com \
--cc=demarchi@kernel$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=rrameshbabu@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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