public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: "Albert L. Lash\, IV" <albert.lash@gmail•com>
Cc: git@vger•kernel.org, "Albert L. Lash\, IV" <alash3@bloomberg•net>
Subject: Re: [PATCH 4/4] docs/git-blame: explain more clearly the example pickaxe use
Date: Mon, 10 Feb 2014 16:21:36 -0800	[thread overview]
Message-ID: <xmqqiosmqz1r.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1391892097-16169-4-git-send-email-alash3@bloomberg.net> (Albert L. Lash, IV's message of "Sat, 8 Feb 2014 15:41:37 -0500")

"Albert L. Lash, IV" <albert.lash@gmail•com> writes:

> 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.

next prev parent reply	other threads:[~2014-02-11  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 20:41 [PATCH 1/4] docs/merge-strategies: remove hyphen from mis-merges Albert L. Lash, IV
2014-02-08 20:41 ` [PATCH 2/4] docs/git-remote: capitalize first word of initial blurb Albert L. Lash, IV
2014-02-08 20:41 ` [PATCH 3/4] docs/git-clone: clarify use of --no-hardlinks option Albert L. Lash, IV
2014-02-11  0:20   ` Junio C Hamano
2014-02-08 20:41 ` [PATCH 4/4] docs/git-blame: explain more clearly the example pickaxe use Albert L. Lash, IV
2014-02-11  0:21   ` Junio C Hamano [this message]
2014-02-10 21:06 ` [PATCH 1/4] docs/merge-strategies: remove hyphen from mis-merges Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqiosmqz1r.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=alash3@bloomberg$(echo .)net \
    --cc=albert.lash@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox