From: Junio C Hamano <gitster@pobox.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] diffcore-pickaxe doc: document -S and -G properly
Date: Tue, 14 May 2013 11:57:47 -0700 [thread overview]
Message-ID: <7v4ne5jsno.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CABURp0r808KeSRwhgPw98vUC+JSErvSYHFyAvn-=8JhQzn8e1Q@mail.gmail.com> (Phil Hord's message of "Tue, 14 May 2013 13:44:58 -0400")
Phil Hord <phil.hord@gmail.com> writes:
> Normally the pickaxe options limit the diff output to those files which
> contained the changes being searched; that is, those files which
> had modifications including the search string. With the --pickaxe-all
> option, the diff of the entire commit will be shown including files
> which did not have modifications including the search string. This
> is designed to make it easier to review the changes in the context
> of the whole commit.
I find this very readable, even though "diff output" might be
somewhat misleading (it is not "output for the end user", but is
"passing to the next stage in the pipeline").
prev parent reply other threads:[~2013-05-14 18:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 14:12 [PATCH] diffcore-pickaxe doc: document -S and -G properly Ramkumar Ramachandra
2013-05-14 17:41 ` Junio C Hamano
2013-05-14 18:20 ` Ramkumar Ramachandra
2013-05-14 18:47 ` Junio C Hamano
2013-05-14 18:57 ` Ramkumar Ramachandra
2013-05-14 19:17 ` Jonathan Nieder
2013-05-14 19:25 ` Ramkumar Ramachandra
2013-05-14 19:29 ` Jonathan Nieder
2013-05-14 19:41 ` Junio C Hamano
2013-05-14 19:31 ` Junio C Hamano
2013-05-14 21:13 ` Phil Hord
2013-05-14 17:44 ` Phil Hord
2013-05-14 17:47 ` Phil Hord
2013-05-14 18:44 ` Ramkumar Ramachandra
2013-05-14 19:19 ` Junio C Hamano
2013-05-14 19:46 ` Ramkumar Ramachandra
2013-05-14 19:53 ` Junio C Hamano
2013-05-14 20:02 ` Ramkumar Ramachandra
2013-05-14 19:23 ` Phil Hord
2013-05-14 18:57 ` Junio C Hamano [this message]
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=7v4ne5jsno.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=phil.hord@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).