aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeremy Kniager <jeremyk@lunarg.com>2020-03-27 09:13:24 -0600
committerjeremyk-lunarg <jeremyk@lunarg.com>2020-03-30 08:23:05 -0600
commita860d5d519bbf2f8d518235c4badbb614198eb08 (patch)
tree4431eedbd7875a51102a6db09e23d77a978bcb16
parent0cf692bf9cbd7b109fc8f5725f14b59a49dcb82f (diff)
downloadusermoji-a860d5d519bbf2f8d518235c4badbb614198eb08.tar.xz
docs: Update clang-format version in docs
Updated the clang-format version in CONTRIBUTING.md: `5.0.0` -> `7.0.0` Change-Id: I4d5cf4b228d3c6a689315a64dc2449c39e17d1bf
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 41e0269e..bad1de23 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -40,7 +40,7 @@ a good reason is "This violates the style guide, but it improves type safety."
* There are `.clang-format` files present in the repository to define clang-format settings
which are found and used automatically by clang-format.
* **clang-format** binaries are available from the LLVM orginization, here: [LLVM](https://clang.llvm.org/). Our CI system (Travis-CI)
- currently uses clang-format version 5.0.0 to check that the lines of code you have changed are formatted properly. It is
+ currently uses clang-format version 7.0.0 to check that the lines of code you have changed are formatted properly. It is
recommended that you use the same version to format your code prior to submission.
* A sample git workflow may look like: