From: M Hickford <mirth.hickford@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Matthew John Cheetham <mjcheetham@outlook.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
M Hickford <mirth.hickford@gmail.com>,
git@vger.kernel.org
Subject: Re: The enduring popularity of git-credential-store
Date: Sun, 28 May 2023 20:33:29 +0100 [thread overview]
Message-ID: <CAGJzqskaM80+8+79yUf435tP93Sk8sFu7marCvyimE=2gOKnog@mail.gmail.com> (raw)
In-Reply-To: <Y3aCx1SYq6jrYfuO@coredump.intra.peff.net>
On Thu, 17 Nov 2022 at 18:51, Jeff King <peff@peff.net> wrote:
>
> On Thu, Nov 17, 2022 at 09:17:53AM -0800, Matthew John Cheetham wrote:
>
> > > In the ideal world, we'd ship an encrypted store that people could use,
> > > but then we have to deal with export regulations and sanctions and
> > > nobody wants to do that. We'd also have to deal with multiple
> > > cryptographic libraries for portability and license reasons and nobody
> > > wants to do that, either.
> >
> > One option rather than shipping (or including in contrib/) any of these
> > credential helpers, could we not reference several other popular helpers
> > in the docs, and let users make their own choice (but at least some are
> > then possibly more discoverable)?
>
> I don't have any problem with documenting the options better. The main
> reason we have store/cache at all, even though they kind of suck, was to
> act as least-common-denominators and pave the way for people making
> better helpers. That happened, but nobody ever went back to adjust the
> docs.
>
> I do think having the docs say "you should go use X" means that X will
> have an advantage over other projects which may compete with it. So I
> think we need to be careful to be inclusive of what we'll mention, and
> to word it so that we're not endorsing any one project.
I agree, although Git for Windows installs Git Credential Manager by
default. Hard to compete with that, but it's fantastic for users.
OAuth credential helpers are so widely useful I think it's worth
introducing them in the documentation. I'll draft a patch.
prev parent reply other threads:[~2023-05-28 19:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 10:50 The enduring popularity of git-credential-store M Hickford
2022-11-08 12:00 ` Michal Suchánek
2022-11-08 15:41 ` Jeff King
2022-11-08 21:03 ` Taylor Blau
2023-02-11 7:11 ` M Hickford
2022-11-08 22:52 ` brian m. carlson
2022-11-12 2:30 ` M Hickford
2022-11-17 17:17 ` Matthew John Cheetham
2022-11-17 18:51 ` Jeff King
2022-11-17 19:29 ` Lessley Dennington
2022-11-17 20:43 ` Jeff King
2023-05-29 9:53 ` M Hickford
2023-05-28 19:33 ` M Hickford [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='CAGJzqskaM80+8+79yUf435tP93Sk8sFu7marCvyimE=2gOKnog@mail.gmail.com' \
--to=mirth.hickford@gmail.com \
--cc=git@vger.kernel.org \
--cc=mjcheetham@outlook.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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.
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).