From: Junio C Hamano <gitster@pobox.com>
To: Aaron Plattner <aplattner@nvidia.com>
Cc: git@vger.kernel.org, Rahul Rameshbabu <rrameshbabu@nvidia.com>
Subject: Re: [PATCH] http: preserve wwwauth_headers across redirects
Date: Tue, 07 Jul 2026 15:35:14 -0700 [thread overview]
Message-ID: <xmqqmrw2zavx.fsf@gitster.g> (raw)
In-Reply-To: <68c2b88f-8976-474b-8965-97733eba5a99@nvidia.com> (Aaron Plattner's message of "Tue, 7 Jul 2026 12:21:27 -0700")
Aaron Plattner <aplattner@nvidia.com> writes:
>> Did anything come of that discussion? No rush, since this change
>> fixes an immediate issue and the helper suggestion is for long-term
>> future-proofing. We can treat them as separate steps.
>>
>> Thanks.
>
> No, I got sidetracked with other work and didn't get a chance to get
> back to this, sorry. It's not directly impacting my users since I can
> just tell them they have to use my server's FQDN, so fine with me to
> treat this as a low-priority issue.
Understood.
I hate to leave a topic backburnered for too long. As this topic
unfortunately has not seen enough attention by reviewers, between
two easy approach available to me to deal with such a topic, namely,
merging it to 'next' and discarding it (with invitation to resubmit
once the author can spend enough time on the topic again), I'd
probably choose the latter.
Unless somebody else steps up and promises to usher the topic
forward in its current shape, that is.
Thanks.
prev parent reply other threads:[~2026-07-07 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 16:11 [PATCH] http: preserve wwwauth_headers across redirects Aaron Plattner
2026-06-03 0:15 ` Junio C Hamano
2026-06-03 0:37 ` Aaron Plattner
2026-07-07 19:16 ` Junio C Hamano
2026-07-07 19:21 ` Aaron Plattner
2026-07-07 22:35 ` Junio C Hamano [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=xmqqmrw2zavx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=aplattner@nvidia.com \
--cc=git@vger.kernel.org \
--cc=rrameshbabu@nvidia.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