[or-cvs] [tor/master 2/3] doc/HACKING: Explain how to find when a given change was introduced

[arma at torproject.org]

Author: Chris Ball <chris at printf.net>
Date: Sat, 31 Jul 2010 19:07:00 -0400
Subject: doc/HACKING: Explain how to find when a given change was introduced
Commit: 16970d83cc8f3cd2f7b7beba9824b7b1b9a716a3

---
 doc/HACKING |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/doc/HACKING b/doc/HACKING
index ac68a35..4eee914 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
-- 
1.7.1