From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jed Brown <jed@59a2.org>,
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 19:15:25 -0700 [thread overview]
Message-ID: <CAJDDKr7BkZjhjPF==v6PWVA4_-HM2cOaj+xusgkLKf7OocEpaw@mail.gmail.com> (raw)
In-Reply-To: <xmqqk3h3pywt.fsf@gitster.dls.corp.google.com>
On Wed, Oct 23, 2013 at 12:31 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jed Brown <jed@59A2.org> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> 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 ;-)
>>
>> I meant that if the proposed migration plan were to be "just change it
>> and people will learn" (because anything more gradual would actually be
>> worse for users) then is it really too late for Git-2.0?
>
> I do not know it that is even a workable plan, but I need to sleep
> on it and then hear opinion from others, but in general, if anybody
> needs to ask if it is too late, then it already is.
Making grep tree-wide would be very welcome here.
IMO Git-2.0 *feels* like a good time to change the default since
there's relatively little downside to doing so, but "early next year"
is not very long to wait either; it doesn't seem like there's a strong
reason to rush this in.
--
David
next prev parent reply other threads:[~2013-10-24 2:15 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
2013-10-23 19:24 ` Jed Brown
2013-10-23 19:31 ` Junio C Hamano
2013-10-24 2:15 ` David Aguilar [this message]
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
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='CAJDDKr7BkZjhjPF==v6PWVA4_-HM2cOaj+xusgkLKf7OocEpaw@mail.gmail.com' \
--to=davvid@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
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).