From: richard.palo@free.fr
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Richard PALO <richard@netbsd.org>,
git@vger.kernel.org, Charles Bailey <charles@hashpling.org>
Subject: Re: git ls-files -o seems to ignore .gitignore
Date: Mon, 27 Oct 2014 10:22:03 +0100 (CET) [thread overview]
Message-ID: <391421950.105620016.1414401723677.JavaMail.root@zimbra7-e1.priv.proxad.net> (raw)
In-Reply-To: <vpq8uk1lxqb.fsf@anie.imag.fr>
Well, ok. Not very intuitive, so I added an alias in .gitconfig...
'ls = ls-files --exclude-standard' and that seems to work now alright for me.
Thanks
----- Mail original -----
> De: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>
> À: "Charles Bailey" <charles@hashpling.org>
> Cc: "Richard PALO" <richard@netbsd.org>, git@vger.kernel.org
> Envoyé: Lundi 27 Octobre 2014 09:31:56
> Objet: Re: git ls-files -o seems to ignore .gitignore
>
> Charles Bailey <charles@hashpling.org> writes:
>
> > On Mon, Oct 27, 2014 at 07:16:49AM +0100, Richard PALO wrote:
> >> 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.
> >
> > This is, as far as I am aware, by design.
>
> I would not call that "by design", but indeed "git ls" was written
> this
> way, and it's a plumbing command for which we do not want
> backward-incompatible changes. So, --exclude-standard is available,
> but
> not activated by default.
>
> --
> Matthieu Moy
> http://www-verimag.imag.fr/~moy/
>
prev parent reply other threads:[~2014-10-27 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 6:16 git ls-files -o seems to ignore .gitignore Richard PALO
2014-10-27 6:47 ` Charles Bailey
2014-10-27 8:31 ` Matthieu Moy
2014-10-27 9:22 ` richard.palo [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=391421950.105620016.1414401723677.JavaMail.root@zimbra7-e1.priv.proxad.net \
--to=richard.palo@free.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=richard@netbsd.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 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).