summaryrefslogtreecommitdiff
path: root/hash.c
diff options
context:
space:
mode:
authorLibravatar Will Palmer <wmpalmer@gmail.com>2010-04-17 17:55:26 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2010-04-17 11:50:32 -0700
commitc308b9c25d54c72977d16155ae04e37f3490d5ac (patch)
treec5a6f4f9019e336df06c73f244f827d542402f08 /hash.c
parentDocumentation/config.txt: default gc.aggressiveWindow is 250, not 10 (diff)
downloadtgif-c308b9c25d54c72977d16155ae04e37f3490d5ac.tar.xz
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>
Diffstat (limited to 'hash.c')
0 files changed, 0 insertions, 0 deletions