Re: [PATCH] grep: --full-tree

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] grep: --full-tree

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:47:46

Jeff King [off-list ref] writes:
On Wed, Nov 25, 2009 at 02:19:35PM -0800, Junio C Hamano wrote:
quoted
Jeff King [off-list ref] writes:
quoted
... That is, I don't want to have to remember "git grep
--full-tree" or "git grep /" every time
But that cuts both ways.  If you change the default to full-tree,
people will forget to put "." every time when asking to limit to the
current directory.
I know. Which is why I am arguing for a configuration option.
Yeah; what is your take on tr/reset-checkout-patch topic, by the way?  I
do not particularly like a configuration that changes the behaviour of a
command in a drastic way---it will make helping others much harder, but I
guess it should be Ok?

This may sound like an OffTopic, but because we _are_ discussing
consistency, it matters.

Re: [PATCH] grep: --full-tree

From: Jeff King <hidden>
Date: 2016-06-15 22:47:46

On Wed, Nov 25, 2009 at 04:02:57PM -0800, Junio C Hamano wrote:
Yeah; what is your take on tr/reset-checkout-patch topic, by the way?  I
do not particularly like a configuration that changes the behaviour of a
command in a drastic way---it will make helping others much harder, but I
guess it should be Ok?

This may sound like an OffTopic, but because we _are_ discussing
consistency, it matters.
It is near the top of my to-review queue. Honestly, despite any
arguments I may have made when the original reset/checkout -p series was
posted, I have been pretty happy with the current behavior. I'll take a
look now and respond in more detail in that thread.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help