summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJ. Ryan Stinnett <jryans@gmail.com>2016-12-08 16:48:00 -1000
committerJ. Ryan Stinnett <jryans@gmail.com>2016-12-08 16:48:00 -1000
commit231564ee5b2862925211234da45c9ccafe201be2 (patch)
tree3d7cc9c21f90d6f211dbd07d0a0b212d0890ecbe /doc
parent39f455468731d4746adb729a67597927beaca4b8 (diff)
downloadtor-231564ee5b2862925211234da45c9ccafe201be2.tar.gz
tor-231564ee5b2862925211234da45c9ccafe201be2.zip
Document no changes file needed for bugfixes on unreleased code
Fixes #20932.
Diffstat (limited to 'doc')
-rw-r--r--doc/HACKING/CodingStandards.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index f1c65850a4..01212a9919 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -93,6 +93,10 @@ What needs a changes file?
rewrites. Anything about which somebody might plausibly wonder "when
did that happen, and/or why did we do that" 6 months down the line.
+What does not need a changes file?
+
+ * Bugfixes for code that hasn't shipped in any released version of Tor
+
Why use changes files instead of Git commit messages?
* Git commit messages are written for developers, not users, and they