doc: mention how to indent source code

Signed-off-by: Daiki Ueno <ueno@gnu.org>

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 37ee2e5e3f508f6a538fbe2aa4c63069718c9f52..d80580614f615ee39ce68f8695a4b286ad65f55b 100644 (file)
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -66,8 +66,8 @@ case by case basis.
 
 # Indentation style:
 
- In general, use [the Linux kernel coding style](https://www.kernel.org/doc/html/latest/process/coding-style.html).
-You may indent the source using GNU indent, e.g. "indent -linux *.c".
+  We use [the Linux kernel coding style](https://www.kernel.org/doc/html/latest/process/coding-style.html). You may indent the source using the
+[devel/indent-gnutls](devel/indent-gnutls) script.
 
 
 # Commenting style

diff --git a/doc/cha-support.texi b/doc/cha-support.texi
index b68cd073f4767a6049653fd78425de17afba03f1..b34c77607979cb1c2a7f80e3f9fff7fa26d2f595 100644 (file)
--- a/doc/cha-support.texi
+++ b/doc/cha-support.texi
@@ -95,13 +95,12 @@ For code contributions, a number of style guides will help you:
 @itemize @bullet
 
 @item Coding Style.
-Follow the GNU Standards document.
-@c (@pxref{top, GNU Coding Standards,,standards}).
+Follow the Linux kernel coding style@footnote{see @uref{https://www.kernel.org/doc/html/latest/process/coding-style.html}.}.
 
 If you normally code using another coding standard, there is no
-problem, but you should use @samp{indent} to reformat the code
-@c (@pxref{top, GNU Indent,, indent}) 
-before submitting your work.
+problem, but you should run the @samp{indent-gnutls} script found in
+the @samp{devel} directory to reformat the code before submitting your
+work.
 
 @item Use the unified diff format @samp{diff -u}.