{"thread":{"id":"23502","subject":"[PATCH v2] documentation: clarify direction of core.autocrlf","startedAt":"2010-04-17T16:55:26Z","lastAt":"2010-04-17T16:55:26Z","messageCount":1,"participants":["Will Palmer"],"isPatch":true,"patchVersion":2,"patchTotal":null},"messages":[{"id":"139757","messageId":"1271523326-6860-1-git-send-email-wmpalmer@gmail.com","threadId":"23502","inReplyTo":null,"subject":"[PATCH v2] documentation: clarify direction of core.autocrlf","fromName":"Will Palmer","fromEmail":"wmpalmer@gmail.com","sentAt":"2010-04-17T16:55:26Z","receivedAt":"2010-04-17T16:55:26Z","isPatch":true,"sender":{"key":"wmpalmer@gmail.com","avatar":"https://avatars.githubusercontent.com/u/357044?v=4"},"body":"The description for core.autocrlf refers to reads from / writes to\n\"the filesystem\", the only use of this rather ambiguous term, which\ntechnically could be referring to the git object database. (All other\nmentions are part of phrases such as \"..filesystems (like NFS)..\").\n\nOther sections, including the section on core.safecrlf, use the term\n\"work tree\" for the same purpose as the term \"the filesystem\" is used in\nthe core.autocrlf section, so that seems like a good alternative, which\nmakes it clearer what direction the addition/removal of CR characters\noccurs in.\n\nSigned-off-by: Will Palmer <wmpalmer@gmail.com>\n---\n Documentation/config.txt |    8 ++++----\n 1 files changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 626b19a..b2a4a92 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -198,11 +198,11 @@ core.quotepath::\n \n core.autocrlf::\n \tIf true, makes git convert `CRLF` at the end of lines in text files to\n-\t`LF` when reading from the filesystem, and convert in reverse when\n-\twriting to the filesystem.  The variable can be set to\n+\t`LF` when reading from the work tree, and convert in reverse when\n+\twriting to the work tree.  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.  A file is considered\n+\treading from the work tree but files are written out to the work\n+\ttree with `LF` at the end of lines.  A file is considered\n \t\"text\" (i.e. be subjected to the autocrlf mechanism) based on\n \tthe file's `crlf` attribute, or if `crlf` is unspecified,\n \tbased on the file's contents.  See linkgit:gitattributes[5].\n-- \n1.7.1.rc1.13.g2f822\n"}]}