git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Jeff King <peff@peff.net>
Cc: M Hickford <mirth.hickford@gmail.com>,
	git@vger.kernel.org,
	Matthew John Cheetham <mjcheetham@github.com>,
	Lessley Dennington <lessleydennington@gmail.com>
Subject: Re: The enduring popularity of git-credential-store
Date: Tue, 8 Nov 2022 16:03:55 -0500	[thread overview]
Message-ID: <Y2rEOxgEskE0seAs@nand.local> (raw)
In-Reply-To: <Y2p4rhiOphuOM0VQ@coredump.intra.peff.net>

On Tue, Nov 08, 2022 at 10:41:34AM -0500, Jeff King wrote:
> So if you're asking "should we stop shipping credential-store", I'm not
> _completely_ opposed, but I do wonder if its popularity means it is
> better-than-nothing for some folks. If you're asking how we can nudge
> people to better systems, that seems like a pure win. But I also don't
> know how to do it. ;)

GCM is such an alternative, but I don't think it necessarily should ship
in the contrib/ tree. I don't love the idea of a banner nudging people
to use arbitrary software in Git's ordinary output, either.

So, I think my point is that there are easy-to-configure alternatives
out there, and they are certainly worth using over what's in contrib in
certain circumstances, but I, too, don't have a good plan on how to
nudge people to try them out.

Thanks,
Taylor

  reply	other threads:[~2022-11-08 21:04 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 [this message]
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

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=Y2rEOxgEskE0seAs@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=lessleydennington@gmail.com \
    --cc=mirth.hickford@gmail.com \
    --cc=mjcheetham@github.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).