summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlbert L. Lash, IV <alash3@bloomberg.net>2014-02-08 15:41:37 -0500
committerJunio C Hamano <gitster@pobox.com>2014-02-11 11:03:07 -0800
commit246090a5d0ff3a51df8fed676e8159c3776c954a (patch)
treefe3a7d1e77f533d6e96d1564330037982d0d73dc
parent897e3e454062d2bb9d3c1e4068caf4971fd713ff (diff)
downloadgit-al/docs.tar.gz
docs/git-blame: explain more clearly the example pickaxe useal/docs
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>
-rw-r--r--Documentation/git-blame.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index 8e70a61840..9f23a861ce 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -35,7 +35,8 @@ Apart from supporting file annotation, Git also supports searching the
development history for when a code snippet occurred in a change. This makes it
possible to track when a code snippet was added to a file, moved or copied
between files, and eventually deleted or replaced. It works by searching for
-a text string in the diff. A small example:
+a text string in the diff. A small example of the pickaxe interface
+that searches for `blame_usage`:
-----------------------------------------------------------------------------
$ git log --pretty=oneline -S'blame_usage'