From: Jonathan Nieder <jrnieder@gmail.com>
To: Hamilton Turner <hamiltont@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Potential bug in ls-files (version 1.7.9.5)
Date: Mon, 7 Jul 2014 15:22:40 -0700 [thread overview]
Message-ID: <20140707222240.GA12427@google.com> (raw)
In-Reply-To: <CAFow3A_f+nPCR1zqS9WdH1V9pNdSP=zRNt2UxbHpOz1d6miQEg@mail.gmail.com>
Hi Hamilton,
Hamilton Turner wrote:
> My project has this directory structure
>
> .
> ├── aspnet
> │ ├── .gitignore
> │ ├── __init__.py
> │ ├── lib
> │ │ ├── <lots of big stuff>
>
> My aspnet/.gitignore lists lib/*, and git add aspnet/lib/foo reports
> that this path is ignored.
>
> But git ls-files --others --ignored --exclude-standard does not list
> the files under lib. These are untracked files, they do show up in
> output if I do git ls-files --others, but not if I provide the ignored
> flag.
>
> With 1.8.5.2, all of the files under lib are listed if I ls-files
> --ignored --others --exclude-standard
This was probably fixed by v1.7.11.2~12^2~5 (ls-files -i: pay
attention to exclusion of leading paths, 2012-06-01).
[...]
> I'm not sure if this 1.7.X is still supported, but I think it's still
> the latest git-core available
> in Ubuntu 12.04 repositories.
I haven't had much luck in the past working with the Ubuntu
maintainers to update old releases. :(
https://launchpad.net/~git-core/+archive/ppa may help if PPAs are
usable in your environment.
Thanks and hope that helps,
Jonathan
prev parent reply other threads:[~2014-07-07 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 21:46 Potential bug in ls-files (version 1.7.9.5) Hamilton Turner
2014-07-07 22:22 ` Jonathan Nieder [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=20140707222240.GA12427@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hamiltont@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.