summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2016-12-16 10:57:37 -0500
committerNick Mathewson <nickm@torproject.org>2016-12-16 10:57:37 -0500
commitb310929ee36f0a88389dca53124506115c850c3b (patch)
treea9601a9d11d368a5a085c217a07b4cdf242fd2b1 /doc
parent812a6581aff4af0503d1e94cb3f0f07df7f36aa2 (diff)
parent231564ee5b2862925211234da45c9ccafe201be2 (diff)
downloadtor-b310929ee36f0a88389dca53124506115c850c3b.tar.gz
tor-b310929ee36f0a88389dca53124506115c850c3b.zip
Merge remote-tracking branch 'jryans/no-changes-unreleased'
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