tor

commit 85219d887dd0e54e9655eff15831839aad304bc0
parent b83c6ab737e403fd555c6fe0e0af6abaa5a48044
Author: Nick Mathewson <nickm@torproject.org>
Date:   Thu, 16 Jul 2020 14:53:03 -0400

Merge remote-tracking branch 'tor-gitlab/mr/57'

Diffstat:
M
doc/HACKING/CodingStandards.md
 | 
12
++++++++++++

1 file changed, 12 insertions(+), 0 deletions(-)
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
@@ -87,6 +87,18 @@ months and expect it to merge cleanly. Try to merge pieces early and often.
 
 ## How we log changes
 
+Before diving in the details on how to write a changes file, note that we do
+NOT require a changes file for:
+
+  * Any change to a file that is not distributed in the tarball. This
+    includes:
+    - Any change to our CI configuration that does not affect the distributed
+      source.
+    - Any change to developer-only tools, unless those tools are distributed
+      in the tarball.
+  * Non-functional code movement.
+  * Identifier re-namings, comment edits, spelling fixes, and so on.
+
 When you do a commit that needs a ChangeLog entry, add a new file to
 the `changes` toplevel subdirectory.  It should have the format of a
 one-entry changelog section from the current ChangeLog file, as in