| commit | 57aa2ffc7dc2865b582058ba661d8b8c4c1e51f4 | |
| author | Will Palmer <wmpalmer@gmail.com> | |
| Tue, 13 Apr 2010 21:56:37 +0000 (13 22:56 +0100) | ||
| committer | Will Palmer <wmpalmer@gmail.com> | |
| Sat, 17 Apr 2010 16:34:45 +0000 (17 17:34 +0100) | ||
| tree | 9c6718340a6c89d0425ddb8bc96e5a020f0c5a75 | treesnapshot (tar.gz zip) |
| parent | cefbb2ff4bb63920f1770b96bd2ddb1f2d736702 | commitdiff |
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>
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>
| Documentation/config.txt | diffblobblamehistory |