From: Mark Lodato <lodatom@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 4/4] grep docs: document --no-index option
Date: Fri, 26 Feb 2010 17:07:48 -0500 [thread overview]
Message-ID: <ca433831002261407l4d708283m5129c582a55fb1b6@mail.gmail.com> (raw)
In-Reply-To: <7vocjceg0y.fsf@alter.siamese.dyndns.org>
On Fri, Feb 26, 2010 at 12:13 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Mark Lodato <lodatom@gmail.com> writes:
>
>> +--no-index::
>> + Search all files in the working tree, not just those tracked by git.
>
> This one is meant to be usable outside git directory, and saying "the
> working tree" is misleading. The "work tree" is a technical term that
> specifically means the files in the directory hierarchy on the filesystem
> that correspond to the index entries that represent them.
>
> It probably should say "the current directory" or something here.
Here's a squashable commit to do just that.
---
Documentation/git-grep.txt | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt
index 86d7401..3e6eaf7 100644
--- a/Documentation/git-grep.txt
+++ b/Documentation/git-grep.txt
@@ -37,7 +37,8 @@ OPTIONS
blobs registered in the index file.
--no-index::
- Search all files in the working tree, not just those tracked by git.
+ Search all files in the current directory, not just those tracked
+ by git.
-a::
--text::
--
1.7.0
prev parent reply other threads:[~2010-02-26 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 3:40 [PATCH 0/4] git-grep documentation updates Mark Lodato
2010-02-26 3:40 ` [PATCH 1/4] grep docs: pluralize "Example" section Mark Lodato
2010-02-26 3:40 ` [PATCH 2/4] grep docs: use AsciiDoc literals consistently Mark Lodato
2010-02-26 3:40 ` [PATCH 3/4] grep docs: --cached and <tree>... are incompatible Mark Lodato
2010-02-26 3:40 ` [PATCH 4/4] grep docs: document --no-index option Mark Lodato
2010-02-26 5:13 ` Junio C Hamano
2010-02-26 22:07 ` Mark Lodato [this message]
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=ca433831002261407l4d708283m5129c582a55fb1b6@mail.gmail.com \
--to=lodatom@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).