[tor-commits] [tor/master] mention lintChanges.py in the coding standards
nickm at torproject.org
nickm at torproject.org
Mon Feb 1 21:49:12 UTC 2016
commit 311a13220cc511a9214cca3b4523b80600288c3b
Author: Nick Mathewson <nickm at torproject.org>
Date: Mon Feb 1 16:47:47 2016 -0500
mention lintChanges.py in the coding standards
---
doc/HACKING/CodingStandards.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index bec0765..4aafa5d 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -80,6 +80,11 @@ When we go to make a release, we will concatenate all the entries
in changes to make a draft changelog, and clear the directory. We'll
then edit the draft changelog into a nice readable format.
+To make sure that stuff is in the right format, we use
+scripts/maint/lintChanges.py to check the changes files for
+(superficial) validity. You can run this script on your own changes
+files!
+
What needs a changes file?
* A not-exhaustive list: Anything that might change user-visible
More information about the tor-commits
mailing list