From: Aaron Plattner <aplattner@nvidia•com>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #05)
Date: Mon, 19 Jan 2026 20:11:38 -0800 [thread overview]
Message-ID: <c54848f2-f389-4eec-953b-c44c3532deaf@nvidia.com> (raw)
In-Reply-To: <xmqqldhybtqs.fsf@gitster.g>
On 1/15/26 10:44 AM, Junio C Hamano wrote:
> * ap/http-probe-rpc-use-auth (2026-01-14) 1 commit
> - remote-curl: use auth for probe_rpc() requests too
>
> HTTP transport failed to authenticate in some code pahts, which has
> been corrected.
>
> Will merge to 'next'?
> source: <20260114163619.614297-2-aplattner@nvidia•com>
Yes please.
prev parent reply other threads:[~2026-01-20 4:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 18:44 What's cooking in git.git (Jan 2026, #05) Junio C Hamano
2026-01-16 7:00 ` Elijah Newren
2026-01-16 15:23 ` Junio C Hamano
2026-01-18 13:42 ` Yee Cheng Chin
2026-01-19 15:44 ` D. Ben Knoble
2026-01-20 4:11 ` Aaron Plattner [this message]
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=c54848f2-f389-4eec-953b-c44c3532deaf@nvidia.com \
--to=aplattner@nvidia$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(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