docs/git-blame: explain more clearly the example pickaxe use
We state that the following paragraph mentions the pickaxe interface, but the term pickaxe is not then used. This change clarifies that the example command uses the pickaxe interface and what it is searching for. Signed-off-by: Albert L. Lash, IV <alash3@bloomberg.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Albert L. Lash, IV committed
Feb 8, 2014 at 15:41 UTC
246090a5d0ff3a51df8fed676e8159c3776c954a
1 file changed
+2
-1
Documentation/git-blame.txt
+2
-1
@@ -35,7 +35,8 @@ Apart from supporting file annotation, Git also supports searching the
35
development history for when a code snippet occurred in a change. This makes it
36
possible to track when a code snippet was added to a file, moved or copied
37
between files, and eventually deleted or replaced. It works by searching for
38
-a text string in the diff. A small example:
38
+a text string in the diff. A small example of the pickaxe interface
39
+that searches for `blame_usage`:
40
41
-----------------------------------------------------------------------------
42
$ git log --pretty=oneline -S'blame_usage'