From 1ac1f048effdfde062de33e4572cd7816e7be03c Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Fri, 13 Aug 2010 17:18:45 -0400 Subject: minor formatting / comment fixes --- doc/HACKING | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/HACKING') diff --git a/doc/HACKING b/doc/HACKING index 4eee914ba9..d8538b1f2c 100644 --- a/doc/HACKING +++ b/doc/HACKING @@ -50,14 +50,14 @@ When you do a commit that needs a ChangeLog entry, add a new file to the "changes" toplevel subdirectory. It should have the format of a one-entry changelog section from the current ChangeLog file, as in - o Major bugfixes: - - Fix a potential buffer overflow. Fixes bug 9999. Bugfix on - Tor 0.3.1.4-beta. + o Major bugfixes: + - Fix a potential buffer overflow. Fixes bug 9999; bugfix on + 0.3.1.4-beta. To write a changes file, first categorize the change. Some common categories are: Minor bugfixes, Major bugfixes, Minor features, Major features, Code -simplifications and refactoring. Then say what the change does. Then, if -it's a bugfix, then mention what bug it fixes and when the bug was +simplifications and refactoring. Then say what the change does. If +it's a bugfix, mention what bug it fixes and when the bug was introduced. To find out which Git tag the change was introduced in, you can use "git describe --contains ". -- cgit v1.2.3-54-g00ecf