Re: git grep: search whole tree by default?
- From
David Aguilar <davvid@gmail.com>
- Date
- Oct 24, 2013, 02:15 UTC
- Message-ID
- <CAJDDKr7BkZjhjPF==v6PWVA4_-HM2cOaj+xusgkLKf7OocEpaw@mail.gmail.com>
- 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:
Show 26 quoted lines
> 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