Re: git grep: search whole tree by default?

Jed Brown [off-list ref] writes:

Junio C Hamano [off-list ref] writes:

quoted

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 [off-list ref] 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.

Junio C Hamano [off-list ref] writes:

Jed Brown [off-list ref] writes:

quoted

Junio C Hamano [off-list ref] writes:

quoted

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?