From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 2/3] api-credentials.txt: mention credential.helper explicitly
Date: Mon, 4 Jun 2012 07:54:42 -0400 [thread overview]
Message-ID: <20120604115442.GB27676@sigill.intra.peff.net> (raw)
In-Reply-To: <1338739804-32167-3-git-send-email-Matthieu.Moy@imag.fr>
On Sun, Jun 03, 2012 at 06:10:03PM +0200, Matthieu Moy wrote:
> The name of the configuration variable was mentioned only at the very
> end of the explanation, in a place specific to a specific rule, hence it
> was not very clear what the specification was about.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---
> Documentation/technical/api-credentials.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/technical/api-credentials.txt b/Documentation/technical/api-credentials.txt
> index 8804c42..4561469 100644
> --- a/Documentation/technical/api-credentials.txt
> +++ b/Documentation/technical/api-credentials.txt
> @@ -179,7 +179,8 @@ credentials from and to long-term storage (where "long-term" is simply
> longer than a single git process; e.g., credentials may be stored
> in-memory for a few minutes, or indefinitely on disk).
>
> -Each helper is specified by a single string. The string is transformed
> +Each helper is specified by a single string in the configuration
> +variable credential.helper. The string is transformed
> by git into a command to be executed using these rules:
They may be in other variables, too (like credential.*.helper). I don't
know if it is worth making that distinction.
Originally, helpers could also use these specification strings to chain
to each other, but in the current implementation, there is no chaining
(it was more important when prompting wasn't automatic, so storage
helpers would chain to prompting helpers). So I think we can disregard
that for now, and they really do just appear in config.
-Peff
next prev parent reply other threads:[~2012-06-04 11:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 16:10 [PATCH 0/3] Improve credential API documentation Matthieu Moy
2012-06-03 16:10 ` [PATCH 1/3] api-credential.txt: show the big picture first Matthieu Moy
2012-06-04 11:51 ` Jeff King
2012-06-03 16:10 ` [PATCH 2/3] api-credentials.txt: mention credential.helper explicitly Matthieu Moy
2012-06-04 11:54 ` Jeff King [this message]
2012-06-04 17:51 ` Matthieu Moy
2012-06-03 16:10 ` [PATCH 3/3] api-credentials.txt: add "see also" section Matthieu Moy
2012-06-03 22:28 ` Junio C Hamano
2012-06-04 11:31 ` Matthieu Moy
2012-06-04 11:56 ` Jeff King
2012-06-04 19:31 ` Junio C Hamano
2012-06-04 20:06 ` Matthieu Moy
2012-06-05 6:59 ` Jeff King
2012-06-05 7:34 ` Jeff King
2012-06-05 11:20 ` Matthieu Moy
2012-06-05 11:22 ` Jeff King
2012-06-05 15:12 ` Junio C Hamano
2012-06-05 15:35 ` Jeff King
2012-06-05 17:28 ` Junio C Hamano
2012-06-04 20:17 ` [PATCH 1/4] doc: fix xref link from api docs to manual pages Matthieu Moy
2012-06-04 20:17 ` [PATCH 2/4 v2] api-credential.txt: show the big picture first Matthieu Moy
2012-06-05 7:36 ` Jeff King
2012-06-04 20:17 ` [PATCH 3/4 v2] api-credentials.txt: mention credential.helper explicitly Matthieu Moy
2012-06-04 20:17 ` [PATCH 4/4 v2] api-credentials.txt: add "see also" section Matthieu Moy
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=20120604115442.GB27676@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).