diff options
| author | Nick Mathewson <nickm@torproject.org> | 2016-02-01 16:47:47 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2016-02-01 16:47:47 -0500 |
| commit | 311a13220cc511a9214cca3b4523b80600288c3b (patch) | |
| tree | ff7c65ef0642c95acf9a90ee4bb32554d3a4f856 | |
| parent | deea08c13f9d6a3dc8eca612ddf09436da1af4f8 (diff) | |
| download | tor-311a13220cc511a9214cca3b4523b80600288c3b.tar.gz tor-311a13220cc511a9214cca3b4523b80600288c3b.zip | |
mention lintChanges.py in the coding standards
| -rw-r--r-- | doc/HACKING/CodingStandards.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index bec076527f..4aafa5ddd4 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 |