author | Junio C Hamano <gitster@pobox.com> | |
Mon, 11 Feb 2008 03:34:34 +0000 (19:34 -0800) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 11 Feb 2008 21:23:15 +0000 (13:23 -0800) | ||
commit | 14f9e128d38f809947d34979a59ee524e350ac6e | |
tree | 44555862335c98d9a3d12ec2c7c22a1917d4b293 | tree | snapshot |
parent | 6fb5375ede25629c23ba2129b48f143e1942e755 | commit | diff |
Define the project whitespace policy
This establishes what the "bad" whitespaces are for this
project.
The rules are:
- Unless otherwise specified, indent with SP that could be
replaced with HT are not "bad". But SP before HT in the
indent is "bad", and trailing whitespaces are "bad".
- For C source files, initial indent by SP that can be replaced
with HT is also "bad".
- Test scripts in t/ and test vectors in its subdirectories can
contain anything, so we make it unrestricted for now.
Anything "bad" will be shown in WHITESPACE error indicator in
diff output, and "apply --whitespace=warn" will warn about it.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This establishes what the "bad" whitespaces are for this
project.
The rules are:
- Unless otherwise specified, indent with SP that could be
replaced with HT are not "bad". But SP before HT in the
indent is "bad", and trailing whitespaces are "bad".
- For C source files, initial indent by SP that can be replaced
with HT is also "bad".
- Test scripts in t/ and test vectors in its subdirectories can
contain anything, so we make it unrestricted for now.
Anything "bad" will be shown in WHITESPACE error indicator in
diff output, and "apply --whitespace=warn" will warn about it.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
.gitattributes | [new file with mode: 0644] | blob |
Documentation/.gitattributes | [new file with mode: 0644] | blob |
t/.gitattributes | [new file with mode: 0644] | blob |