git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jeff King <peff@peff.net>
Cc: "Taylor Blau" <me@ttaylorr.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
	"Leonardo Bras" <leobras.c@gmail.com>,
	git@vger.kernel.org, "Jan Viktorin" <viktorin@rehivetech.com>,
	"Michal Nazarewicz" <mina86@mina86.com>
Subject: Re: [PATCH] send-email: Defines smtpPassCmd config option
Date: Sun, 3 May 2020 16:27:57 +0000	[thread overview]
Message-ID: <20200503162757.GE6530@camp.crustytoothpaste.net> (raw)
In-Reply-To: <20200503094348.GE170902@coredump.intra.peff.net>

[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]

On 2020-05-03 at 09:43:48, Jeff King wrote:
> On Fri, May 01, 2020 at 11:59:48PM +0000, brian m. carlson wrote:
> 
> > I think perhaps many folks aren't aware that you can invoke Git with an
> > arbitrary shell command as "credential.helper", which of course makes
> > life a lot easier.  So if you want to invoke a separate command, it's
> > really as easy as this:
> > 
> >   git config credential.smtp://smtp.crustytoothpaste.net.helper \
> >     '!f() { echo username=my-username; echo "password=$(my-password-command)"; }; f'
> > 
> > So I think that documenting the use of the credential helper is step 1,
> > because probably most people _do_ want to use that for their passwords,
> > and then documenting that credential helpers can be arbitrary shell
> > commands that speak the protocol is step 2, so that people who don't can
> > figure out a way to do what they want.
> > 
> > I'll send some patches later which document the latter feature, since I
> > don't think we mention it anywhere outside of the FAQ.  I actually
> > didn't know about it until Peff mentioned it to me one time.
> 
> This is documented, but only recently did it make it out of
> Documentation/technical/ and into gitcredentials(7). I don't mind adding
> more pointers, though.

Ah, yes, I remembered that series, but forgot that it introduced
documentation for that.

I'll just send a patch that updates the config option to mention the
other cases, since we already document it in gitcredentials(7).
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2020-05-03 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 10:51 [PATCH] send-email: Defines smtpPassCmd config option Leonardo Bras
2020-05-01 12:53 ` Carlo Marcelo Arenas Belón
2020-05-01 15:50   ` Junio C Hamano
2020-05-01 22:27     ` Taylor Blau
2020-05-01 23:59       ` brian m. carlson
2020-05-03  9:43         ` Jeff King
2020-05-03 16:27           ` brian m. carlson [this message]
2020-05-03 23:48             ` Carlo Marcelo Arenas Belón
2020-05-04 19:49         ` Leonardo Bras
2020-05-04 20:35           ` Jeff King
2020-05-04 21:29             ` Leonardo Bras
2020-05-04 19:09     ` Leonardo Bras
2020-05-04 19:02   ` Leonardo Bras

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=20200503162757.GE6530@camp.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=leobras.c@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=mina86@mina86.com \
    --cc=peff@peff.net \
    --cc=viktorin@rehivetech.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.
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).