From: Jonathan Nieder <jrnieder@gmail.com>
To: Woody Gilk <woody.gilk@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git file listing is inconsistent
Date: Wed, 26 Nov 2014 13:55:20 -0800 [thread overview]
Message-ID: <20141126215520.GS6527@google.com> (raw)
In-Reply-To: <CAGOJM6+DTSn2qa-KTWceqyraaugX_YVZhirkdc+t+cDfFB4OyQ@mail.gmail.com>
Hi Woody,
Woody Gilk wrote:
> git diff --name-only
> git grep --files-with-matches
>
> I think --files-with-matches should be deprecated and replaced with
> --name-only for consistency.
See the (non-git) diff(1) and grep(1) manpages.
It might make sense for 'git grep' to learn --name-only too as a
synonym to help muscle memory, though.
*looks*
Actually, 'git grep -h' tells me that git grep --name-only is already
accepted as a synonym for --files-with-matches, ever since
$ git log -Sname-only -- builtin-grep.c
[...]
commit 2cd5dfd240ecb63c77bcb2532664984e3b69ae47
Author: Shawn O. Pearce <spearce@spearce.org>
Date: Wed Feb 20 23:28:07 2008 -0500
Teach git-grep --name-only as synonym for -l
I expected git grep --name-only to give me only the file names,
much as git diff --name-only only generates filenames. Alas the
option is -l, which matches common external greps but doesn't match
other parts of the git UI.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
(v1.5.5-rc0~171). Have you tried it?
Would something like the following patch help?
-- >8 --
Subject: grep doc: add reminder about --name-only option
Since v1.5.5-rc0~171 (2008-02-20), "git grep" accepts --name-only
as a synonym for the GNU-style --files-with-matches, but because the
synonym is not mentioned in the manpage synopsis it is hard to find.
Reported-by: Woody Gilk <woody.gilk@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
Documentation/git-grep.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt
index 31811f1..8060efe 100644
--- a/Documentation/git-grep.txt
+++ b/Documentation/git-grep.txt
@@ -14,7 +14,7 @@ SYNOPSIS
[-E | --extended-regexp] [-G | --basic-regexp]
[-P | --perl-regexp]
[-F | --fixed-strings] [-n | --line-number]
- [-l | --files-with-matches] [-L | --files-without-match]
+ [-l | --files-with-matches | --name-only] [-L | --files-without-match]
[(-O | --open-files-in-pager) [<pager>]]
[-z | --null]
[-c | --count] [--all-match] [-q | --quiet]
--
2.2.0.rc0.207.ga3a616c
next prev parent reply other threads:[~2014-11-26 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 21:10 git file listing is inconsistent Woody Gilk
2014-11-26 21:47 ` Junio C Hamano
2014-11-26 21:55 ` Jonathan Nieder [this message]
2014-11-26 22:01 ` Woody Gilk
2014-11-26 21:59 ` Scott Schmit
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141126215520.GS6527@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=woody.gilk@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.