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 2/2] diffcore-pickaxe doc: document -S and -G properly
Date: Fri, 24 May 2013 09:54:19 -0700 [thread overview]
Message-ID: <7v8v34b9ok.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CABURp0qCOMJnQ=+p81eXLtj6+zujO=MsYODx8zR_cXjVXwV=HA@mail.gmail.com> (Phil Hord's message of "Fri, 24 May 2013 10:58:29 -0400")
Phil Hord <phil.hord@gmail.com> writes:
> On Fri, May 24, 2013 at 5:37 AM, Ramkumar Ramachandra
> <artagnon@gmail.com> wrote:
>> Junio C Hamano wrote:
>>> [...]
>>
>> I agree with the other comments, and have made suitable changes.
>> Let's review your block now.
>>
>>> This transformation is used to find filepairs that represent
>>> two kinds of changes, and is controlled by the -S, -G and
>>> --pickaxe-all options.
>>
>> Why do you call this a "transformation"? Is git log --author="foo" a
>> transformation on the git-log output? Then how is git log -Sfoo a
>> transformation?
>>
>> Two kinds of changes controlled by three different options? Isn't the
>> original much clearer?
>
> They are all three filters. They transform the output by limiting it
> to commits which meet specific conditions. Transformation is used in
> the network-graphs sense of the word. It fits the beginning of the
> document where it says this:
>
> The diffcore mechanism is fed a list of such comparison results
> (each of which is called "filepair", although at this point each
> of them talks about a single file), and transforms such a list
> into another list. There are currently 5 such transformations:
>
> - diffcore-break
> - diffcore-rename
> - diffcore-merge-broken
> - diffcore-pickaxe
> - diffcore-order
Thanks.
next prev parent reply other threads:[~2013-05-24 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 12:23 [PATCH v2 0/2] Improve diffcore-pickaxe documentation Ramkumar Ramachandra
2013-05-17 12:23 ` [PATCH 1/2] diffcore-pickaxe: make error messages more consistent Ramkumar Ramachandra
2013-05-18 1:25 ` Junio C Hamano
2013-05-17 12:23 ` [PATCH 2/2] diffcore-pickaxe doc: document -S and -G properly Ramkumar Ramachandra
2013-05-18 1:24 ` Junio C Hamano
2013-05-19 7:33 ` Junio C Hamano
2013-05-24 9:37 ` Ramkumar Ramachandra
2013-05-24 14:58 ` Phil Hord
2013-05-24 16:01 ` Ramkumar Ramachandra
2013-05-24 16:54 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-24 10:33 [PATCH v3 0/2] Improve diffcore-pickaxe documentation Ramkumar Ramachandra
2013-05-24 10:33 ` [PATCH 2/2] diffcore-pickaxe doc: document -S and -G properly Ramkumar Ramachandra
2013-05-24 17:31 ` Junio C Hamano
2013-05-31 12:04 ` Ramkumar Ramachandra
2013-06-02 19:56 ` Junio C Hamano
2013-06-02 20:28 ` Ramkumar Ramachandra
2013-05-31 12:12 [PATCH v4 0/2] Improve diffcore-pickaxe documentation Ramkumar Ramachandra
2013-05-31 12:12 ` [PATCH 2/2] diffcore-pickaxe doc: document -S and -G properly Ramkumar Ramachandra
2013-06-03 17:54 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v8v34b9ok.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).