summaryrefslogtreecommitdiffstats
path: root/src/gtest
diff options
context:
space:
mode:
authorEric Engestrom <eric@engestrom.ch>2016-08-30 21:02:18 +0100
committerEric Anholt <eric@anholt.net>2016-08-31 17:06:54 -0700
commit3bd885d09cea6ecf19ddfd948c8dd74f5e3ea600 (patch)
tree0c02e91c24673553459195bf642ca1adc188c533 /src/gtest
parent509e2dbc105a04e8bc6ed292b921cbe27957a779 (diff)
downloadexternal_mesa3d-3bd885d09cea6ecf19ddfd948c8dd74f5e3ea600.zip
external_mesa3d-3bd885d09cea6ecf19ddfd948c8dd74f5e3ea600.tar.gz
external_mesa3d-3bd885d09cea6ecf19ddfd948c8dd74f5e3ea600.tar.bz2
Introduce .editorconfig
A few weeks ago, Jose Fonseca suggested [0] we use .editorconfig files to try and enforce the formatting of the code, to which Michel Dänzer suggested [1] we start by importing the existing .dir-locals.el settings. The first draft was discussed in the RFC [2]. These .editorconfig are a first step, one that has the advantage of requiring little to no intervention from the devs once the settings files are in place, but the settings are very limited. This does have the advantage of applying while the code is being written. This doesn't replace the need for more comprehensive formatting tools such as clang-format & clang-tidy, but those reformat the code after the fact. [0] https://lists.freedesktop.org/archives/mesa-dev/2016-June/121545.html [1] https://lists.freedesktop.org/archives/mesa-dev/2016-June/121639.html [2] https://lists.freedesktop.org/archives/mesa-dev/2016-July/123431.html Acked-by: Nicolai Hähnle <nicolai.haehnle@amd.com> Acked-by: Eric Anholt <eric@anholt.net> Signed-off-by: Eric Engestrom <eric@engestrom.ch> Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
Diffstat (limited to 'src/gtest')
-rw-r--r--src/gtest/.editorconfig3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/gtest/.editorconfig b/src/gtest/.editorconfig
new file mode 100644
index 0000000..0880bac
--- /dev/null
+++ b/src/gtest/.editorconfig
@@ -0,0 +1,3 @@
+[*.{cc,h}]
+indent_style = space
+indent_size = 2