From: Junio C Hamano <gitster@pobox.com>
To: Jed Brown <jed@59A2.org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git grep: search whole tree by default?
Date: Wed, 23 Oct 2013 11:52:06 -0700 [thread overview]
Message-ID: <xmqqob6fq0q1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <87hac7hmrb.fsf@mcs.anl.gov> (Jed Brown's message of "Wed, 23 Oct 2013 13:20:56 -0500")
Jed Brown <jed@59A2.org> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>> I suspect that it would be too late for 2.0 we want to do sometime
>> early next year, though.
>
> How would you manage transition from the current behavior? Warning
> people to explicitly use "." or ":/" during some interim period sounds
> worse than just switching the default behavior.
"How would I"?
You're asking that question only because you omitted too much from
the quote ;-)
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
> In summary: changing is painful. The case of "git add" was really bad,
> since the same command had different behavior depending on the options
> given, so it was clearly worth the pain. In the case of "git grep", the
> current behavior is not _that_ bad, so nobody bothered to do the change.
>
> (by "do the change", I mean propose a migration plan, convince people
> that it is good, ...)
I agree that it is up to those who really want to switch the
default.
next prev parent reply other threads:[~2013-10-23 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 8:25 git grep: search whole tree by default? Piotr Krukowiecki
2013-10-23 16:21 ` Matthieu Moy
2013-10-23 17:23 ` Junio C Hamano
2013-10-23 18:20 ` Jed Brown
2013-10-23 18:52 ` Junio C Hamano [this message]
2013-10-23 19:24 ` Jed Brown
2013-10-23 19:31 ` Junio C Hamano
2013-10-24 2:15 ` David Aguilar
2013-10-23 20:43 ` Matthieu Moy
2013-10-24 2:27 ` Jeff King
2013-10-24 19:40 ` Junio C Hamano
2013-10-25 2:23 ` David Aguilar
2013-10-25 4:37 ` Jeff King
2013-10-25 4:52 ` Duy Nguyen
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=xmqqob6fq0q1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=jed@59A2.org \
--cc=piotr.krukowiecki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.