From: Miles Bader <miles@gnu.org>
To: Yann Dirson <dirson@bertin.fr>
Cc: gitster@pobox.com, git list <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)
Date: Mon, 06 Dec 2010 17:13:46 +0900 [thread overview]
Message-ID: <buopqtfmi85.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <20101206082948.1403cc5a@chalon.bertin.fr> (Yann Dirson's message of "Mon, 06 Dec 2010 08:29:48 +0100")
Yann Dirson <dirson@bertin.fr> writes:
> But then, why not simply use --find-renames (since --detect-renames has
> luckily not been released ontl the masses yet), and avoid making similar-usage
> opts dissimilar and then adding a synonym just to make them similar the other
> way ?
"Find" and "detect" have different nuances.
"Detect" sounds somewhat passive/minor, so "detect renames" makes it
more clear that renames are detected _in addition_ to normal processing.
"Find," by contrast, is active/major, so "find renames" makes it sounds
like an action to be performed _instead_ of some normal processing.
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2010-12-06 8:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 6:30 What's cooking in git.git (Dec 2010, #01; Sat, 4) Junio C Hamano
2010-12-05 7:39 ` Jeff King
2010-12-05 19:54 ` Junio C Hamano
2010-12-06 0:54 ` aleksi.aalto
2010-12-09 17:27 ` Jeff King
2010-12-10 19:55 ` Junio C Hamano
2010-12-05 10:13 ` Yann Dirson
2010-12-05 20:23 ` Junio C Hamano
2010-12-06 7:29 ` Yann Dirson
2010-12-06 8:13 ` Miles Bader [this message]
2010-12-06 8:21 ` Yann Dirson
2010-12-06 8:39 ` Miles Bader
2010-12-06 8:48 ` Yann Dirson
2010-12-06 9:13 ` Miles Bader
2010-12-06 11:31 ` Yann Dirson
2010-12-06 11:37 ` Matthieu Moy
2010-12-10 21:59 ` Junio C Hamano
2010-12-05 12:36 ` aleksi.aalto
2010-12-05 15:51 ` Patrick Rouleau
2010-12-05 13:00 ` Erik Faye-Lund
2010-12-05 20:15 ` Junio C Hamano
2010-12-05 15:00 ` Michael J Gruber
2010-12-05 20:06 ` Junio C Hamano
2010-12-06 8:55 ` Michael J Gruber
2010-12-06 15:39 ` Thiago Farina
2010-12-08 11:23 ` t9010 broken in pu [Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)] Thomas Rast
2010-12-08 11:28 ` Jonathan Nieder
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=buopqtfmi85.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=dirson@bertin.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).