Re: [PATCH 4/4] docs/git-blame: explain more clearly the example pickaxe use
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Feb 11, 2014, 00:21 UTC
- Message-ID
- <xmqqiosmqz1r.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <1391892097-16169-4-git-send-email-alash3@bloomberg.net>
"Albert L. Lash, IV" <albert.lash@gmail.com> writes:
Show 24 quoted lines
> 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> > --- > Documentation/git-blame.txt | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt > index 8e70a61..ddb88d0 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'
Thanks.
I cannot shake this nagging feeling that this and the latter half of the previous paragraph may not belong to this page, though.
Will queue.