From: Jeff King <peff@peff.net>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: Re: [PATCH] docs: document credential.helper allowed values
Date: Wed, 6 May 2020 12:27:58 -0400 [thread overview]
Message-ID: <20200506162758.GC1275237@coredump.intra.peff.net> (raw)
In-Reply-To: <20200505231226.1280264-1-sandals@crustytoothpaste.net>
On Tue, May 05, 2020 at 11:12:26PM +0000, brian m. carlson wrote:
> gitcredentials(7) already mentions several possible invocations that one
> can use as the value for credential.helper. However, many people are
> not aware that there are other options than a simple credential helper
> name, so let's place some explanatory text in the documentation for
> credential.helper as well.
>
> We still refer the user to gitcredential(7) for additional explanations
> and helpful examples.
Yeah, this seems like an improvement to me.
-Peff
prev parent reply other threads:[~2020-05-06 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 23:12 [PATCH] docs: document credential.helper allowed values brian m. carlson
2020-05-06 0:30 ` Carlo Marcelo Arenas Belón
2020-05-06 16:27 ` Jeff King [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=20200506162758.GC1275237@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--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