* HACKING: Hint at old commits with `git describe' output.

diff --git a/ChangeLog b/ChangeLog
index 48c6e79a26f55e700944cc2b8463b2869ce5a14a..7b64d5503e266993eb70ea5f82383302c755b211 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2010-09-13  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       * HACKING: Hint at old commits with `git describe' output.
+
 2010-09-12  Stefano Lattarini  <stefano.lattarini@gmail.com>
 
        Fix regression in test `colon4.test'.

diff --git a/HACKING b/HACKING
index d9b2099a7e0679121c17ca1e0054c6e1276ad0cf..ecbd0a8ce5c43b0aaf0bc3fdf853d4a145511810 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -143,6 +143,8 @@
   the active branches descending from the buggy commit.  This offers a
   simple way to fix the bug consistently and effectively.
 
+* When referring to older commits, use 'git describe' output as pointer.
+
 * There may be a number of longer-lived feature branches for new developments.
   They should be based off of a common ancestor of all active branches to
   which the feature should be merged later.  The next branch may serve as