[tor-commits] [tor/master] Document no changes file needed for bugfixes on unreleased code

[nickm@xxxxxxxxxxxxxx]

commit 231564ee5b2862925211234da45c9ccafe201be2
Author: J. Ryan Stinnett <jryans@xxxxxxxxx>
Date:   Thu Dec 8 16:48:00 2016 -1000

    Document no changes file needed for bugfixes on unreleased code
    
    Fixes #20932.
---
 doc/HACKING/CodingStandards.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index f1c6585..01212a9 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



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits