diff options
| author | Chris Ball <chris@printf.net> | 2010-07-31 19:07:00 -0400 |
|---|---|---|
| committer | Sebastian Hahn <sebastian@torproject.org> | 2010-08-12 02:38:58 +0200 |
| commit | 16970d83cc8f3cd2f7b7beba9824b7b1b9a716a3 (patch) | |
| tree | 4850c5fa5a990fa660f5ca0dcf22ad8e29cf1618 /doc/HACKING | |
| parent | 28962ecae852dc1f7cbd5c084bb5feb9e37ca9f5 (diff) | |
| download | tor-16970d83cc8f3cd2f7b7beba9824b7b1b9a716a3.tar.gz tor-16970d83cc8f3cd2f7b7beba9824b7b1b9a716a3.zip | |
doc/HACKING: Explain how to find when a given change was introduced
Diffstat (limited to 'doc/HACKING')
| -rw-r--r-- | doc/HACKING | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/HACKING b/doc/HACKING index ac68a35a08..4eee914ba9 100644 --- a/doc/HACKING +++ b/doc/HACKING @@ -58,7 +58,8 @@ 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 -introduced. +introduced. To find out which Git tag the change was introduced in, +you can use "git describe --contains <sha1 of commit>". If at all possible, try to create this file in the same commit where you are making the change. Please give it a distinctive name that no |