Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Define the project whitespace policy

This establishes what the "bad" whitespaces are for this

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 <>
  • Loading branch information...
commit 14f9e128d38f809947d34979a59ee524e350ac6e 1 parent 6fb5375
@gitster gitster authored
2  .gitattributes
@@ -0,0 +1,2 @@
+* whitespace=!indent,trail,space
+*.[ch] whitespace
1  Documentation/.gitattributes
@@ -0,0 +1 @@
+*.txt whitespace
1  t/.gitattributes
@@ -0,0 +1 @@
+* -whitespace
Please sign in to comment.
Something went wrong with that request. Please try again.