From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: M Hickford via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, M Hickford <mirth.hickford@gmail.com>
Subject: Re: [PATCH] Mention that password could be a personal access token.
Date: Thu, 27 Oct 2022 14:48:33 -0700 [thread overview]
Message-ID: <xmqqo7txj5u6.fsf@gitster.g> (raw)
In-Reply-To: <Y1roZeM6EsPgpHqu@coredump.intra.peff.net> (Jeff King's message of "Thu, 27 Oct 2022 16:21:57 -0400")
Jeff King <peff@peff.net> writes:
> FWIW, I had the same reaction. From the client perspective for https,
> this is going over basic-auth, and it might be nice to just say so. But
> of course the whole credential system is abstract, so it gets awkward.
> We could probably say something like:
>
> The credential's password, if we are asking it to be stored. Note that
> this may not strictly be a traditional password, but rather any secret
> string which is used for authentication. For instance, Git's HTTP
> protocol will generally pass this using an Authorization header;
> depending on what the server is expecting this may be a password typed
> by the user, a personal access token, or some other opaque value.
Thanks. I have no problem with this replacement text.
> Maybe that is getting too into the weeds. OTOH, anybody reading this far
> into git-credential(1) is probably pretty technical.
True, too.
next prev parent reply other threads:[~2022-10-27 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:45 [PATCH] Mention that password could be a personal access token M Hickford via GitGitGadget
2022-10-27 17:40 ` Junio C Hamano
2022-10-27 20:21 ` Jeff King
2022-10-27 21:48 ` Junio C Hamano [this message]
2022-11-01 3:54 ` M Hickford
2022-11-01 7:58 ` Ævar Arnfjörð Bjarmason
2022-11-01 10:27 ` M Hickford
2022-11-02 10:30 ` [PATCH v2] " M Hickford via GitGitGadget
2022-11-02 10:54 ` Eric Sunshine
2022-11-02 15:44 ` Junio C Hamano
2022-11-02 15:51 ` Eric Sunshine
2022-11-02 17:30 ` Philip Oakley
2022-11-08 12:11 ` M Hickford
2022-11-08 13:01 ` [PATCH v3] " M Hickford via GitGitGadget
2022-11-08 21:48 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo7txj5u6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mirth.hickford@gmail.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).