From: Nick Mathewson Date: Mon, 1 Feb 2016 21:47:47 +0000 (-0500) Subject: mention lintChanges.py in the coding standards X-Git-Tag: tor-0.2.8.1-alpha~18 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=311a13220cc511a9214cca3b4523b80600288c3b;p=thirdparty%2Ftor.git mention lintChanges.py in the coding standards --- 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