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

diff --git a/ChangeLog b/ChangeLog
index 48c6e79..7b64d55 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 d9b2099..ecbd0a8 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