aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-04-20 00:52:34 -0400
committerNick Mathewson <nickm@torproject.org>2010-04-27 12:24:35 -0400
commit8ec5f939a6dd48d93ab5535b207e454b0b990ab3 (patch)
tree554ebeb886b717e36d15ebc55b1a554db9715dc8 /changes
parentb92ef5fa0e7aa121f6ee2456a0241b93fe6c453d (diff)
downloadtor-8ec5f939a6dd48d93ab5535b207e454b0b990ab3.tar.gz
tor-8ec5f939a6dd48d93ab5535b207e454b0b990ab3.zip
Add new sections to the HACKING file
The main changes are to explain how we use git branches, how we use changes files, and what should go into a patch. Putting these in HACKING means that we shouldn't need to constantly refer to the or-dev emails where we explain this stuff.
Diffstat (limited to 'changes')
-rw-r--r--changes/revise_HACKING4
1 files changed, 4 insertions, 0 deletions
diff --git a/changes/revise_HACKING b/changes/revise_HACKING
new file mode 100644
index 0000000000..7cc68a1668
--- /dev/null
+++ b/changes/revise_HACKING
@@ -0,0 +1,4 @@
+ o Documentation:
+ - Convert the HACKING file to asciidoc, and add a few new sections
+ to it, explaining how we use Git, how we make changelogs, and
+ what should go in a patch.