diff options
| author | Chelsea H. Komlo <chelsea.komlo@gmail.com> | 2016-12-21 11:42:05 -0500 |
|---|---|---|
| committer | Chelsea H. Komlo <chelsea.komlo@gmail.com> | 2016-12-21 17:05:18 -0500 |
| commit | d95678ca8f97ac6e648598af01b4394840999e72 (patch) | |
| tree | 3fcf91d7905b06c4c73070b2a8bd62d6ac8d8d8a /doc | |
| parent | 064b1b6d1c2beca282dd878e7fa869d1dff1eea3 (diff) | |
| download | tor-d95678ca8f97ac6e648598af01b4394840999e72.tar.gz tor-d95678ca8f97ac6e648598af01b4394840999e72.zip | |
make distcheck should be a part of the local development process
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/HACKING/CodingStandards.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index 009047d6a3..9932c77353 100644 --- a/doc/HACKING/CodingStandards.md +++ b/doc/HACKING/CodingStandards.md @@ -8,6 +8,7 @@ tl;dr: - Document your functions - Write unit tests - Run `make test-full` to test against all unit and integration tests. + - Run `make distcheck` to ensure the distribution works - Add a file in `changes` for your branch. Patch checklist @@ -29,6 +30,7 @@ Did you remember... - To write unit tests, as possible? - To run `make test-full` to test against all unit and integration tests (or `make test-full-online` if you have a working connection to the internet)? + - To test that the distribution will actually work via `make distcheck`? - To base your code on the appropriate branch? - To include a file in the `changes` directory as appropriate? |