From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>,
Duy Nguyen <pclouds@gmail.com>
Subject: Re: [PATCH v6] Add new git-related helper to contrib
Date: Thu, 23 May 2013 10:05:26 -0700 [thread overview]
Message-ID: <7v38tdhbjd.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAMP44s1e-kjVnAHQx3GOAG6ge_GZBmOBaCnr8YeyU6t5CveuzA@mail.gmail.com> (Felipe Contreras's message of "Wed, 22 May 2013 22:50:39 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Wed, May 22, 2013 at 10:23 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> This doesn't make any sense:
>
> Ah, never mind, it's COPYING the one being modified, not EXTRACTING.
Yes.
The different levels of -C happens to correspond to the software
engineering practice from best to sloppy:
- When you refactor to have a block of lines in a file , the
original of that block would have come from another file (or the
same file) you touched to remove duplication, so a single -C
looks for an origin only from modified files (best).
- When you start a new file, you may have to start from some
boilerplate material that already exists in another file that is
not (and does not have to be) changed in the commit you add that
new file, so double -C -C looks for an origin of lines from other
files, even unmodified ones, when looking at the lines in a new
file (unfortunate but acceptable).
- When you copy and paste without making any effort to refactor,
you modify a file by adding new lines that match identically from
another existing file, the latter of which does not change in the
commit you do that copy and paste. To find this, you need to
look for an origin for any file from all the other files, and
triple -C -C -C lets you do so (sloppy).
next prev parent reply other threads:[~2013-05-23 17:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 15:53 [PATCH v6] Add new git-related helper to contrib Felipe Contreras
2013-05-20 1:47 ` Eric Sunshine
2013-05-22 19:23 ` Junio C Hamano
2013-05-22 19:54 ` Junio C Hamano
2013-05-22 22:23 ` Felipe Contreras
2013-05-22 22:38 ` Junio C Hamano
2013-05-22 22:43 ` Felipe Contreras
2013-05-22 22:53 ` Junio C Hamano
2013-05-22 22:58 ` Junio C Hamano
2013-05-22 23:42 ` Junio C Hamano
2013-05-22 23:57 ` Felipe Contreras
2013-05-23 0:08 ` Junio C Hamano
2013-05-23 4:07 ` Felipe Contreras
2013-05-23 5:22 ` Felipe Contreras
2013-05-23 16:54 ` Junio C Hamano
2013-05-23 18:34 ` Junio C Hamano
2013-05-23 21:33 ` Felipe Contreras
2013-05-23 21:52 ` Junio C Hamano
2013-05-23 21:58 ` Felipe Contreras
2013-05-23 22:44 ` Junio C Hamano
2013-05-23 22:59 ` Felipe Contreras
2013-05-23 23:47 ` Junio C Hamano
2013-05-24 0:22 ` Felipe Contreras
2013-05-23 3:23 ` Felipe Contreras
2013-05-23 3:50 ` Felipe Contreras
2013-05-23 17:05 ` Junio C Hamano [this message]
2013-05-22 23:19 ` Felipe Contreras
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=7v38tdhbjd.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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