From: David Aguilar <davvid@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Jed Brown <jed@59a2.org>,
Piotr Krukowiecki <piotr.krukowiecki@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git grep: search whole tree by default?
Date: Thu, 24 Oct 2013 19:23:49 -0700 [thread overview]
Message-ID: <CAJDDKr5G_dpk5s6EMBF=iU+yHkr7TKYRUBJAxBQY9Y9jy6FmCA@mail.gmail.com> (raw)
In-Reply-To: <xmqqd2muo3sz.fsf@gitster.dls.corp.google.com>
On Thu, Oct 24, 2013 at 12:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Jeff King <peff@peff.net> writes:
>
>> That would also provide people who do not like the change of default an
>> escape hatch to keep the current behavior. And I do not think scripted
>> use will be inconvenienced; they will already have to use "." or ":/" to
>> be explicit (if they care) since the behavior is changing.
>
> There is a big difference between "scripted use will have an escape
> hatch" and "scripted use will not be inconvenienced". We *know*
> scripts will be inconvenienced with or without such a configuration
> variable, as they *have* to be updated if they rely on the current
> behaviour of "git grep" that limits its search to the current
> directory when fed no pathspec (and if their users want to keep the
> current behaviour of such scripts). Anything short of a warning (or
> even erroring out) that is designed to annoy the users during the
> transition period will help ease the pain of transition of scripts.
>
> An annoying warning still can only *ease*, but cannot eliminate, the
> pain of transition. The scripts need to be updated to adjust to the
> new behaviour; there is no getting around to it.
>
> Even if we ignore the "helping your colleague at her terminal", cf.
>
> http://thread.gmane.org/gmane.comp.version-control.git/133570/focus=133683
>
> issue for now, adding a new configuration variable from day one
> makes the transition of scripts somewhat worse, I am afraid. Doing
> so robs us a way to add such an annoying warning to help people
> foresee problems in their existing scripts before the default
> changes (the configuration presumably will disable the "this command
> line will behave differently after the default changes" warning).
>
> As I said, I think we can train people without an annoying warning,
> as hits outside their current directory will serve as an annoyance
> already, and people who set such a configuration in their repository
> (or $HOME/.gitconfig), get used to the chosen behaviour too much,
> and get surprised when they get to use a vanilla intallation of Git
> (either helping colleague or setting up a new work environment) have
> only themselves to blame, so it may not be too big a deal.
>
> But I do not think the same reasoning extends to scripted uses X-<.
The set of people that script "git grep" may in fact be pretty low /
almost non-existent so it may be a non-issue, but here's my one data
point:
For git-cola, this change in behavior would not make any difference.
It already jumps to the top-level during startup so its grep feature
is unaffected.
It'd be good to hear from other script writers but that's my $.02.
--
David
next prev parent reply other threads:[~2013-10-25 2:23 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
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 [this message]
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='CAJDDKr5G_dpk5s6EMBF=iU+yHkr7TKYRUBJAxBQY9Y9jy6FmCA@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=peff@peff.net \
--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).