Procházet zdrojové kódy

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

Chris Ball před 15 roky
rodič
revize
16970d83cc
1 změnil soubory, kde provedl 2 přidání a 1 odebrání
  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
 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