documentation: clarify direction of core.autocrlf
The description for core.autocrlf refers to reads from / writes to "the filesystem", the only use of this rather ambiguous term, which technically could be referring to the git object database. (All other mentions are part of phrases such as "..filesystems (like NFS).."). Other sections, including the section on core.safecrlf, use the term "work tree" for the same purpose as the term "the filesystem" is used in the core.autocrlf section, so that seems like a good alternative, which makes it clearer what direction the addition/removal of CR characters occurs in. Signed-off-by: Will Palmer <wmpalmer@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Will Palmer committed
Apr 17, 2010 at 17:55 UTC
c308b9c25d54c72977d16155ae04e37f3490d5ac
1 file changed
+4
-4
Documentation/config.txt
+4
-4
@@ -198,11 +198,11 @@ core.quotepath::
198
199
core.autocrlf::
200
If true, makes git convert `CRLF` at the end of lines in text files to
201
- `LF` when reading from the filesystem, and convert in reverse when
202
- writing to the filesystem. The variable can be set to
201
+ `LF` when reading from the work tree, and convert in reverse when
202
+ writing to the work tree. The variable can be set to
203
'input', in which case the conversion happens only while
204
- reading from the filesystem but files are written out with
205
- `LF` at the end of lines. A file is considered
204
+ reading from the work tree but files are written out to the work
205
+ tree with `LF` at the end of lines. A file is considered
206
"text" (i.e. be subjected to the autocrlf mechanism) based on
207
the file's `crlf` attribute, or if `crlf` is unspecified,
208
based on the file's contents. See linkgit:gitattributes[5].