From: Richard PALO <richard@netbsd.org>
To: git@vger.kernel.org
Subject: git ls-files -o seems to ignore .gitignore
Date: Mon, 27 Oct 2014 07:16:49 +0100 [thread overview]
Message-ID: <544DE351.9060800@netbsd.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm having an issue in that 'git ls-files -o' seems to ignore
[parts of] .gitignore whereas other commands, such as 'git status'
seem fine.
Here is an example:
> richard@omnis:/home/richard/src/pkgsrc$ export LANG=C
> richard@omnis:/home/richard/src/pkgsrc$ git --version git version
> 2.1.2 richard@omnis:/home/richard/src/pkgsrc$ cat .gitignore
> pkgchk*.conf* .#* README*.html
> richard@omnis:/home/richard/src/pkgsrc$ git status On branch dev
>
> It took 6.82 seconds to enumerate untracked files. 'status -uno'
> may speed it up, but you have to be careful not to forget to add
> new files yourself (see 'git help status'). nothing to commit,
> working directory clean richard@omnis:/home/richard/src/pkgsrc$ git
> ls-files -o |grep -c README 12393
Known issue?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJUTeNRAAoJECAB22fHtp27hckH+wdDHV3oZqatSIqNdhUCUxsJ
jR8tZpQxoKfV944aPBgH4/CXkCtFFSvnGKfH+plij+Y5ggZwfDQ3lXIg1qOsH3qj
9mvudRuFxwujXfFSTHdReqQxFT8p3roZjB0GdwoiFeBIsQ8CLfGjxfQZDQU18i3/
IfR682UbzuiR6kodhD5oX/I2S5l5dRRuabQq5t2zJL9BHmGleLaBgOjnne7T26PC
JpNMt+60J93J9VzBN9kQABAO5BMUE4mN6g2141N9JXlMsg6DSGHPN5vQD7t7IxE1
mtNX9iMrjFa1Hsm2neXqvjb95ZGbZwTnxFcI7To6P3V/+v9QMpKrrBWu/AFNdF0=
=84q1
-----END PGP SIGNATURE-----
next reply other threads:[~2014-10-27 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 6:16 Richard PALO [this message]
2014-10-27 6:47 ` git ls-files -o seems to ignore .gitignore Charles Bailey
2014-10-27 8:31 ` Matthieu Moy
2014-10-27 9:22 ` richard.palo
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=544DE351.9060800@netbsd.org \
--to=richard@netbsd.org \
--cc=git@vger.kernel.org \
/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.