core.autocrlf documentation: mention the crlf attribute

The description of the configuration variable is obsolete and
wrong (saying only file content is used), not just incomplete.
It has used the attribute mechanism for a long time.

The documentation of gitattributes mentions the core.autocrlf
configuration variable in its description of crlf attribute.
Refer to the gitattributes documentation from here as well.

Signed-off-by: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Matthew Ogilvie 2009-11-14 11:35:00 -07:00 committed by Junio C Hamano
parent 78d553b7d7
commit ff68668695

View File

@ -169,9 +169,10 @@ core.autocrlf::
writing to the filesystem. The variable can be set to writing to the filesystem. The variable can be set to
'input', in which case the conversion happens only while 'input', in which case the conversion happens only while
reading from the filesystem but files are written out with reading from the filesystem but files are written out with
`LF` at the end of lines. Currently, which paths to consider `LF` at the end of lines. A file is considered
"text" (i.e. be subjected to the autocrlf mechanism) is "text" (i.e. be subjected to the autocrlf mechanism) based on
decided purely based on the contents. the file's `crlf` attribute, or if `crlf` is unspecified,
based on the file's contents. See linkgit:gitattributes[5].
core.safecrlf:: core.safecrlf::
If true, makes git check if converting `CRLF` as controlled by If true, makes git check if converting `CRLF` as controlled by