From: Michael J Gruber <git@drmicha.warpmail.net>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: b5227d8 changes meaning of "ls-files -x 'pattern'"
Date: Mon, 14 Dec 2009 17:15:38 +0100 [thread overview]
Message-ID: <4B2664AA.4050204@drmicha.warpmail.net> (raw)
In-Reply-To: <2e24e5b90912140751y5d769f15pa6782914bdb04dbd@mail.gmail.com>
Sitaram Chamarty venit, vidit, dixit 14.12.2009 16:51:
> Hello,
>
> Before b5227d8, the following two commands would produce different
> outputs (say on git.git):
>
> git ls-files
> git ls-files -x '*.c'
>
> From b5227d8 onward, they produce the same output. The second command
> no longer excludes *.c files.
>
> I was unable to understand the commit message completely but it sounds
> like this was intentionally changed to do this.
Yes. Generally, git commands never ignore tracked files, and this patch
reintroduces this for git ls-files
> I've never been real clear on ls-files, and was wondering if someone
> would be able to clarify the various ways of using it, including why
> this change was made and is there a way (using some other combination of
> flags perhaps) to get a list of files without *.c (to continue this
> example).
You can still use file glob patterns as the file argument, such as
git ls-files '*.[^c]'
Michael
next prev parent reply other threads:[~2009-12-14 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 15:51 b5227d8 changes meaning of "ls-files -x 'pattern'" Sitaram Chamarty
2009-12-14 16:15 ` Michael J Gruber [this message]
2009-12-14 18:25 ` Jeff King
2009-12-17 12:54 ` Sitaram Chamarty
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=4B2664AA.4050204@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=sitaramc@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.