From 7e57cf2c8f8026aca7c93e5b26e92b01d6ccb41b Mon Sep 17 00:00:00 2001
From: Silke Hofstra <silke@slxh.eu>
Date: Sat, 3 Oct 2020 15:41:17 +0200
Subject: [PATCH] CONTRIBUTING: add --no-backup to uncrustify

---
 CONTRIBUTING.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1a664e34e6..910db5fcc7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -105,9 +105,12 @@ It is possible to check if your code follows these conventions:
 * You can [uncrustify] `.c` and `.h` files:
 
   ```console
-  $ uncrustify -c $RIOTBASE/uncrustify-riot.cfg <your file>
+  $ uncrustify -c $RIOTBASE/uncrustify-riot.cfg --no-backup <your file>
   ```
 
+  **Note**: The `--no-backup` flag makes uncrustify *replace* the current file
+   with a formatted version.
+
 * RIOT provides static test tools to verify the quality of changes (cppcheck,
   trailing whitespaces, documentation, etc). These tools are wrapped in a
   single `make` target: `static-test`.