@@ -340,13 +340,13 @@ To avoid waiting until you've made a PR to find formatting issues, you can
340340install clang-format locally and run it against your code as you are working.
341341
342342Different versions of clang-format have slightly different behaviors. CBMC uses
343- clang-format-7 as it is available the repositories for Ubuntu 18.04 and
343+ clang-format-10 as it is available the repositories for Ubuntu 18.04 and
344344Homebrew.
345345To install on a Unix-like system, try installing using the system package
346346manager:
347347```
348- apt-get install clang-format-7 # Run this on Ubuntu, Debian etc.
349- brew install clang-format@7 # Run this on a Mac with Homebrew installed
348+ apt-get install clang-format-10 # Run this on Ubuntu, Debian etc.
349+ brew install clang-format@10 # Run this on a Mac with Homebrew installed
350350```
351351
352352If your platform doesn't have a package for clang-format, you can download a
@@ -358,12 +358,12 @@ the [LLVM Snapshot Builds page](http://llvm.org/builds/).
358358
359359### FORMATTING A RANGE OF COMMITS
360360
361- Clang-format is distributed with a driver script called git-clang-format-7 .
361+ Clang-format is distributed with a driver script called git-clang-format.
362362This script can be used to format git diffs (rather than entire files).
363363
364364After committing some code, it is recommended to run:
365365```
366- git-clang-format-7 upstream/develop
366+ git-clang-format upstream/develop
367367```
368368* Important:* If your branch is based on a branch other than ` upstream/develop ` ,
369369use the name or checksum of that branch instead. It is strongly recommended to
@@ -373,7 +373,7 @@ rebase your work onto the tip of the branch it's based on before running
373373Note: By default, git-clang-format uses the git config variable
374374` clangformat.binary ` . If you have multiple versions of clang-format installed,
375375you might need to update this, or explicitly specify the binary to use via
376- ` --binary clang-format-7 ` .
376+ ` --binary clang-format-10 ` .
377377
378378### RETROACTIVELY FORMATTING INDIVIDUAL COMMITS
379379
@@ -385,7 +385,7 @@ The following command will stop at each commit in the range and run
385385clang-format on the diff at that point. This rewrites git history, so it's
386386* unsafe* , and you should back up your branch before running this command:
387387```
388- git filter-branch --tree-filter 'git-clang-format-7 upstream/develop' \
388+ git filter-branch --tree-filter 'git-clang-format upstream/develop' \
389389 -- upstream/develop..HEAD
390390```
391391* Important* : ` upstream/develop ` should be changed in * both* places in the
0 commit comments