From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/1] Fix netrc usage with WebDAV-based HTTP protocol
Date: Mon, 24 Feb 2025 22:09:52 +0000 [thread overview]
Message-ID: <Z7zuMBVrnX_pLE0K@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqa5ab70ka.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On 2025-02-24 at 16:46:29, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > However, I think we need to either decide that we're going to support
> > this as a fully-fledged feature and add documentation and sufficient
> > tests, or remove it, since it's not reasonable to have undocumented,
> > untested features that people rely on.
>
> Does "this" refer to "use of netrc in HTTP code paths", or "HTTP
> walker"? I am kind of surprised that anybody is still using the
> latter, regardless of where the credential is locally stored.
It refers to netrc in HTTP code paths.
There are definitely people using the WebDAV-based HTTP protocol still,
but after reading the comment in the code that implies that we don't
read packed-refs, I'm less and less inclined to say that's a good idea.
It's probably going to die pretty quickly when we move to reftable,
though, since that protocol only works with the files backend.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2025-02-24 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 21:34 [Bug] git-http-push authentication fails using netrc-file since v2.46 Peter Georg
2025-02-18 22:53 ` brian m. carlson
2025-02-23 1:53 ` [PATCH 0/1] Fix netrc usage with WebDAV-based HTTP protocol brian m. carlson
2025-02-23 1:53 ` [PATCH 1/1] http: allow using netrc for " brian m. carlson
2025-02-24 16:46 ` [PATCH 0/1] Fix netrc usage with " Junio C Hamano
2025-02-24 22:09 ` brian m. carlson [this message]
2025-02-26 12:38 ` Peter Georg
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=Z7zuMBVrnX_pLE0K@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.