{"thread":{"id":"14717","subject":"[PATCH] Updated the Documentation/config.txt core.autocrlf configuration setting documentation","startedAt":"2008-07-28T11:48:14Z","lastAt":"2008-07-28T11:48:14Z","messageCount":1,"participants":["Jurko Gospodnetić"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"85279","messageId":"g6kbm1$gbp$1@ger.gmane.org","threadId":"14717","inReplyTo":null,"subject":"[PATCH] Updated the Documentation/config.txt core.autocrlf configuration setting documentation","fromName":"Jurko Gospodnetić","fromEmail":"jurko.gospodnetic@docte.hr","sentAt":"2008-07-28T11:48:14Z","receivedAt":"2008-07-28T11:48:14Z","isPatch":true,"sender":{"key":"jurko.gospodnetic@docte.hr","avatar":null},"body":"    Hi all.\n\n    This is just a fix for something in the documentation that confused \nme when playing around with git.\n\n--- Comment: --------\n    Updated the Documentation/config.txt core.autocrlf configuration\nsetting documentation to note that this setting can be set at a\nrepository or file level by using the gitattributes configuration.\n\nSigned-off-by: Jurko <jurko.gospodnetic@docte.hr>\n---------------------\n\n    Diff is attached as a separate file.\n\n    Still have not figured out how to best send in patches (working on\nWindows here) so this one is a manually sent mail and you will most\nlikely not be able to apply it automatically. :-(\n\n    I am also not sure whether there are perhaps any other documentation\ncopies that need to be updated for this. This was the only one I found\nin the source tree.\n\n    Best regards,\n      Jurko Gospodnetić\n\n\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 1a13abc..d9c1401 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -135,9 +135,10 @@ core.autocrlf::\n \twriting to the filesystem.  The variable can be set to\n \t'input', in which case the conversion happens only while\n \treading from the filesystem but files are written out with\n-\t`LF` at the end of lines.  Currently, which paths to consider\n-\t\"text\" (i.e. be subjected to the autocrlf mechanism) is\n-\tdecided purely based on the contents.\n+\t`LF` at the end of lines.  Which paths to consider \"text\" (i.e. be subjected\n+    to the autocrlf mechanism) will be decided based on the contents but this\n+    can be overruled on a per-repository or per-file level by using\n+    linkgit:gitattributes[5].\n \n core.safecrlf::\n \tIf true, makes git check if converting `CRLF` as controlled by\n"}]}