From: "Jeremy Ramer" <jdramer@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "James Cloos" <cloos@jhcloos.com>,
git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Caleb Cushing" <xenoterracide@gmail.com>
Subject: Re: ls-files [Was: Re: Fwd: git status options feature suggestion]
Date: Thu, 9 Oct 2008 16:13:07 -0600 [thread overview]
Message-ID: <b9fd99020810091513j21d37e0y94a387cd6d72bd2@mail.gmail.com> (raw)
In-Reply-To: <20081009214118.GZ8203@spearce.org>
On Thu, Oct 9, 2008 at 3:41 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> James Cloos <cloos@jhcloos.com> wrote:
>> >>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>> >> > How about "git ls-files -o"?
>> >>
>> >> doh... hadn't even heard of that command.
>>
>> Johannes> Which is good! As ls-files is listed as plumbing.
>> Johannes> Users should not need to call ls-files,
>>
>> That is a bug, then. ls-files is one of the more important user-level
>> commands in git.
>>
>> It is vastly more efficient than find(1) or a --recursive call to
>> grep(1).
>
> How about using "git grep" then? No need for ls-files...
I use git-grep for searching the contents of files in the repo, but it
seems to me that git ls-files is necessary for quickly parsing the
file names themselves.
>
> --
> Shawn.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-10-09 22:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 5:34 git status options feature suggestion Caleb Cushing
2008-10-09 6:11 ` Jeff King
[not found] ` <81bfc67a0810082327p421ca4e9v84f4b33023bc6fe6@mail.gmail.com>
2008-10-09 6:27 ` Fwd: " Caleb Cushing
2008-10-09 9:03 ` Johannes Schindelin
2008-10-09 15:12 ` Michael J Gruber
2008-10-10 2:20 ` Caleb Cushing
2008-10-10 4:25 ` Elijah Newren
2008-10-10 11:13 ` Johannes Schindelin
2008-10-12 4:49 ` Jeff King
2008-10-12 6:41 ` Junio C Hamano
2008-10-12 6:45 ` Jeff King
2008-10-12 8:10 ` Junio C Hamano
2008-10-13 1:04 ` Jeff King
2008-10-13 1:30 ` Shawn O. Pearce
2008-10-26 1:47 ` Junio C Hamano
2008-10-26 4:59 ` Jeff King
2008-10-12 18:05 ` Shawn O. Pearce
2008-10-13 1:06 ` Jeff King
2008-10-12 9:07 ` Jakub Narebski
2008-10-12 10:47 ` Wincent Colaiuta
2008-10-12 11:40 ` Teemu Likonen
2008-10-12 13:52 ` Andreas Ericsson
2008-10-12 8:26 ` Fwd: " Jeff King
2008-10-12 9:58 ` Junio C Hamano
2008-10-13 0:59 ` Jeff King
2008-10-09 21:23 ` ls-files [Was: Re: Fwd: git status options feature suggestion] James Cloos
2008-10-09 21:41 ` Shawn O. Pearce
2008-10-09 22:13 ` Jeremy Ramer [this message]
2008-10-09 22:52 ` ls-files James Cloos
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=b9fd99020810091513j21d37e0y94a387cd6d72bd2@mail.gmail.com \
--to=jdramer@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=xenoterracide@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 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).