mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2025-02-24 14:51:11 +01:00
Code Issues Projects Releases Wiki Activity

Stop mentioning src/or and src/common in doc/HACKING

Browse source
This commit is contained in:
Nick Mathewson 2018-07-10 11:03:45 -04:00
parent 23dc770f87
commit fa2d53aa6a
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/HACKING/CodingStandards.md
View file

@ -200,8 +200,8 @@ We have some wrapper functions like `tor_malloc`, `tor_free`, `tor_strdup`, and
always succeed or exit.) always succeed or exit.)
You can get a full list of the compatibility functions that Tor provides by You can get a full list of the compatibility functions that Tor provides by
looking through `src/common/util*.h` and `src/common/compat*.h`. You can see the looking through `src/lib/*/*.h`. You can see the
available containers in `src/common/containers*.h`. You should probably available containers in `src/lib/containers/*.h`. You should probably
familiarize yourself with these modules before you write too much code, or familiarize yourself with these modules before you write too much code, or
else you'll wind up reinventing the wheel. else you'll wind up reinventing the wheel.

4
doc/HACKING/Module.md
View file

@ -96,8 +96,8 @@ There are couples of "rules" you want to follow:
filename as the one in the module. For example, this is a bad idea and filename as the one in the module. For example, this is a bad idea and
should never be done: should never be done:
- `src/or/shared_random.c` - `src/feature/dirclient/shared_random.c`
- `src/or/dirauth/shared_random.c` - `src/feature/dirauth/shared_random.c`
* When you include headers from the module, **always** use the full module * When you include headers from the module, **always** use the full module
path in your statement. Example: path in your statement. Example: