Просмотр исходного кода

doc/HACKING: Explain how to find when a given change was introduced

Chris Ball 15 лет назад
Родитель
Сommit
16970d83cc
1 измененных файлов с 2 добавлено и 1 удалено
  1. 2 1
      doc/HACKING

+ 2 - 1
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
 are: Minor bugfixes, Major bugfixes, Minor features, Major features, Code
 simplifications and refactoring.  Then say what the change does.  Then, if
 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
 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
 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
 you are making the change.  Please give it a distinctive name that no