From 9c3d13fd60e149d05740bb9f97edd0f0ca7a5a5d Mon Sep 17 00:00:00 2001
From: "W. Trevor King" <wking@tremily.us>
Date: Fri, 1 Jun 2012 13:19:02 -0400
Subject: [PATCH] Mention `git describe` in my Git notes.

---
 posts/Git/notes.org | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/posts/Git/notes.org b/posts/Git/notes.org
index d9dd589..73fee98 100644
--- a/posts/Git/notes.org
+++ b/posts/Git/notes.org
@@ -794,7 +794,11 @@ previous commit
     : 33db5f4d9027a10e477ccf054b2c1ab94f74c85a tags/v0.99~940
 
 Now you are wiser, because you know that it happened 940 revisions
-before v0.99.
+before v0.99.  A similar command is =git describe=, which finds the
+latest tag in a commit's history and uses that to construct a name:
+
+    : $ git describe v1.0.5^2
+    : tags/v1.0.0-21-g975b31d
 
 ** List unmerged commits
 
-- 
2.26.2