Merge branch 'jk/autocrlf-overrides-eol-doc'

Documentation around core.crlf has been updated.

* jk/autocrlf-overrides-eol-doc:
docs/config: clarify "text property" in core.eol
doc/gitattributes: clarify "autocrlf overrides eol"

diff --combined Documentation/gitattributes.txt
index a2310fb920ecf64cacf6617c97383bbc4443a03c,ce383e97dcc33377ffa79bd6304c0495fdab5979..9b41f81c06ef9fd2386b0e424d4d62cb27195ae3
--- 1/Documentation/gitattributes.txt
--- 2/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@@ -124,7 -124,9 +124,9 @@@ text file is normalized, its line endin
  repository.  To control what line ending style is used in the working
  directory, use the `eol` attribute for a single file and the
  `core.eol` configuration variable for all text files.
- Note that `core.autocrlf` overrides `core.eol`
+ Note that setting `core.autocrlf` to `true` or `input` overrides
+ `core.eol` (see the definitions of those options in
+ linkgit:git-config[1]).
  
  Set::
  
@@@ -344,9 -346,7 +346,9 @@@ automatic line ending conversion based 
  
  Use the following attributes if your '*.ps1' files are UTF-16 little
  endian encoded without BOM and you want Git to use Windows line endings
 -in the working directory. Please note, it is highly recommended to
 +in the working directory (use `UTF-16-LE-BOM` instead of `UTF-16LE` if
 +you want UTF-16 little endian with BOM).
 +Please note, it is highly recommended to
  explicitly define the line endings with `eol` if the `working-tree-encoding`
  attribute is used to avoid ambiguity.