From: Jeff King <peff@peff.net>
To: Lessley Dennington <lessleydennington@gmail.com>
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: Thu, 17 Nov 2022 15:43:33 -0500 [thread overview]
Message-ID: <Y3ac9ZuvpDJO3k9F@coredump.intra.peff.net> (raw)
In-Reply-To: <a76a5e37-0c0a-b9e8-13cb-abaa44cf8911@gmail.com>
On Thu, Nov 17, 2022 at 11:29:35AM -0800, Lessley Dennington wrote:
> On 11/17/22 10:51 AM, Jeff King wrote:
> > 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.
> >
> > -Peff
>
> Completely agree with this. I've long wished for a page on git-scm.com
> that's dedicated to (1) explaining what a credential helper is and
> (2) offering a list of suggested helpers along with scenarios for which
> each is best-suited. This could also be a good place to call out the risks
> of using helpers like git-credential-store in a factual, unbiased way.
It's also a nice place because it's easier to keep up-to-date compared
to say, a manpage.
-Peff
next prev parent reply other threads:[~2022-11-17 20:43 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 [this message]
2023-05-29 9:53 ` M Hickford
2023-05-28 19:33 ` M Hickford
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=Y3ac9ZuvpDJO3k9F@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=lessleydennington@gmail.com \
--cc=mirth.hickford@gmail.com \
--cc=mjcheetham@outlook.com \
--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.
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).