Changes between Version 54 and Version 55 of Submitting/C

Timestamp:

Feb 6, 2022, 3:11:24 AM (2 years ago)

Author:

neteler

Comment:

update link to ​https://github.com/OSGeo/grass/blob/main/utils/grass_indent.sh

Submitting/C

@@ -287 +287 @@
 }}}
 
-Existing code should not be re-indented as this will make "diff" comparisons with older versions impossible. In extreme cases, when run of `indent` tool is necessary, do not commit (check in) any changes other than the indentation in the same commit. Additionally, add the `indent` tool switches and any indent warning messages to the SVN commit message (SVN log). Any change or fix mixed in with an indentation is very hard to track making it hard for others to follow the change, fix any new bugs or track the origin of particular lines (`svn diff --ignore-space-change` is helpful in this case, but does not solve the problem).
-
-For your convenience use the [source:grass/trunk/tools/grass_indent.sh tools/grass_indent.sh] script available in GRASS source code.
+Existing code should not be re-indented as this will make "diff" comparisons with older versions impossible. In extreme cases, when run of `indent` tool is necessary, do not commit (check in) any changes other than the indentation in the same commit. Additionally, add the `indent` tool switches and any indent warning messages to the commit message (`git log`). Any change or fix mixed in with an indentation is very hard to track making it hard for others to follow the change, fix any new bugs or track the origin of particular lines (`git diff --ignore-space-change` is helpful in this case, but does not solve the problem).
+
+For your convenience use the [https://github.com/OSGeo/grass/blob/main/utils/grass_indent.sh grass_indent.sh] script available in GRASS source code.
 
 See [http://grasswiki.osgeo.org/wiki/Development#Explanation_of_C_indentation_rules GRASS Wiki] or `man indent` for explanation of individual switches.