kernel
/
git
mirror of https://git.kernel.org/pub/scm/git/git.git
1
0
Fork 0
Code Releases Activity

docs/credential: minor clarity fixups 

The text in git-credential(1) was copied from
technical/api-credentials, so it still talks about the
input/output format as coming from git to the helper. Since
the surrounding text already indicates that this format is
used for reading and writing with git credential, we can
just remove the extraneous confusing bits.

Signed-off-by: Jeff King <peff@peff.net>
Acked-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
Jeff King 2012-07-18 08:04:02 -04:00 committed by Junio C Hamano
parent 6a9aa0c9b2
commit 3e5f29e896
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/git-credential.txt
View File

@ -102,22 +102,20 @@ INPUT/OUTPUT FORMAT
------------------- -------------------


`git credential` reads and/or writes (depending on the action used) `git credential` reads and/or writes (depending on the action used)
credential information in its standard input/output. These information credential information in its standard input/output. This information
can correspond either to keys for which `git credential` will obtain can correspond either to keys for which `git credential` will obtain
the login/password information (e.g. host, protocol, path), or to the the login/password information (e.g. host, protocol, path), or to the
actual credential data to be obtained (login/password). actual credential data to be obtained (login/password).


The credential is split into a set of named attributes. The credential is split into a set of named attributes, with one
Attributes are provided to the helper, one per line. Each attribute is attribute per line. Each attribute is
specified by a key-value pair, separated by an `=` (equals) sign, specified by a key-value pair, separated by an `=` (equals) sign,
followed by a newline. The key may contain any bytes except `=`, followed by a newline. The key may contain any bytes except `=`,
newline, or NUL. The value may contain any bytes except newline or NUL. newline, or NUL. The value may contain any bytes except newline or NUL.
In both cases, all bytes are treated as-is (i.e., there is no quoting, In both cases, all bytes are treated as-is (i.e., there is no quoting,
and one cannot transmit a value with newline or NUL in it). The list of and one cannot transmit a value with newline or NUL in it). The list of
attributes is terminated by a blank line or end-of-file. attributes is terminated by a blank line or end-of-file.
Git will send the following attributes (but may not send all of Git understands the following attributes:
them for a given credential; for example, a `host` attribute makes no
sense when dealing with a non-network protocol):


`protocol`:: `protocol`::