summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-07-10 10:03:22 -0400
committerNick Mathewson <nickm@torproject.org>2017-07-10 10:03:22 -0400
commit9ec9589c3a5123c957471d3bcbd6219bdfb070c7 (patch)
tree01d30b14ec6cf5b2e74049efb63c6850b865e265
parentdb71d42868fd57904840d10e49ee28bbb3b25039 (diff)
parent934f85f87aa17bf6e1ffad37df8d8d4fb7bf404e (diff)
downloadtor-9ec9589c3a5123c957471d3bcbd6219bdfb070c7.tar.gz
tor-9ec9589c3a5123c957471d3bcbd6219bdfb070c7.zip
Merge remote-tracking branch 'chelseakomlo/coding-standards-22762'
-rw-r--r--doc/HACKING/CodingStandards.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index da8ce62f5e..cc1ba8e773 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -7,7 +7,7 @@ tl;dr:
- Document your functions
- Write unit tests
- Run `make check` before submitting a patch
- - Run `make distcheck` to ensure the distribution works
+ - Run `make distcheck` if you have made changes to build system components
- Add a file in `changes` for your branch.
Patch checklist
@@ -37,6 +37,11 @@ If you are submitting a major patch or new feature, or want to in the future...
- Set up Chutney and Stem, see HACKING/WritingTests.md
- Run `make test-full` to test against all unit and integration tests.
+If you have changed build system components:
+ - Please run `make distcheck`
+ - For example, if you have changed Makefiles, autoconf files, or anything
+ else that impacts the build system.
+
How we use Git branches
=======================