[PATCH] Updated the Documentation/config.txt core.autocrlf configuration setting documentation

From: Jurko Gospodnetić <jurko.gospodnetic@docte.hr>
Date: Jul 28, 2008, 11:48 UTC
Message-ID: <g6kbm1$gbp$1@ger.gmane.org>

    Hi all.

    This is just a fix for something in the documentation that confused 
me when playing around with git.

--- Comment: --------
    Updated the Documentation/config.txt core.autocrlf configuration
setting documentation to note that this setting can be set at a
repository or file level by using the gitattributes configuration.

Signed-off-by: Jurko <jurko.gospodnetic@docte.hr>
---------------------

    Diff is attached as a separate file.

    Still have not figured out how to best send in patches (working on
Windows here) so this one is a manually sent mail and you will most
likely not be able to apply it automatically. :-(

    I am also not sure whether there are perhaps any other documentation
copies that need to be updated for this. This was the only one I found
in the source tree.

    Best regards,
      Jurko Gospodnetić

diff --git a/Documentation/config.txt b/Documentation/config.txt
index 1a13abc..d9c1401 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -135,9 +135,10 @@ core.autocrlf::
 	writing to the filesystem.  The variable can be set to
 	'input', in which case the conversion happens only while
 	reading from the filesystem but files are written out with
-	`LF` at the end of lines.  Currently, which paths to consider
-	"text" (i.e. be subjected to the autocrlf mechanism) is
-	decided purely based on the contents.
+	`LF` at the end of lines.  Which paths to consider "text" (i.e. be subjected
+    to the autocrlf mechanism) will be decided based on the contents but this
+    can be overruled on a per-repository or per-file level by using
+    linkgit:gitattributes[5].
 
 core.safecrlf::
 	If true, makes git check if converting `CRLF` as controlled by