git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git grep: search whole tree by default?
Date: Wed, 23 Oct 2013 18:21:00 +0200	[thread overview]
Message-ID: <vpqbo2guff7.fsf@anie.imag.fr> (raw)
In-Reply-To: <CAA01CsqgNKdDAc9OL9zdk=3tnK9GAG=6w+wP_XSoiefBOgfzRQ@mail.gmail.com> (Piotr Krukowiecki's message of "Wed, 23 Oct 2013 10:25:55 +0200")

Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:

> I think there were discussion about how there are several git commands
> which do not search in whole tree by default and that it's going to be
> changed. I think "add" is one of such commands. Is 'grep' left
> unchanged?

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'd personally be slightly in favor of changing to tree-wide, but
without strong opinion.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  reply	other threads:[~2013-10-23 16:21 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 [this message]
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
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=vpqbo2guff7.fsf@anie.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.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).