From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Raúl Núñez de Arenas Coronado" <raulnac@gmail.com>, git@vger.kernel.org
Subject: Re: Fwd: Unexpected behavior of ls-files command when using --others --exclude-from, and a .gitignore file which resides in a subdirectory
Date: Mon, 22 Jan 2024 13:45:05 -0800 [thread overview]
Message-ID: <xmqq1qa9rqji.fsf@gitster.g> (raw)
In-Reply-To: <20240122213410.GA811766@coredump.intra.peff.net> (Jeff King's message of "Mon, 22 Jan 2024 16:34:10 -0500")
Jeff King <peff@peff.net> writes:
> PS I hadn't realized that --exclude-per-directory had been marked as
> deprecated. I do agree with e750951e74 (ls-files: guide folks to
> --exclude-standard over other --exclude* options, 2023-01-13) in its
> goal of guiding people to the easiest option, but I don't know that
> there has been any discussion about removing the other ones.
I do not think there is any value in _removing_ the perfectly well
working --exclude* options, even though I think --exclude-standard
should be what users and scriptors should be using if they want to
emulate what Git does internally.
next prev parent reply other threads:[~2024-01-22 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGF1KhWNaO_TUuCPo2L_HzNnR+FnB1Q4H6_xQ2owoH+SnynzEg@mail.gmail.com>
2024-01-22 20:45 ` Fwd: Unexpected behavior of ls-files command when using --others --exclude-from, and a .gitignore file which resides in a subdirectory Raúl Núñez de Arenas Coronado
2024-01-22 20:52 ` Junio C Hamano
2024-01-22 21:07 ` Raúl Núñez de Arenas Coronado
2024-01-22 21:42 ` Junio C Hamano
2024-01-23 6:08 ` Raúl Núñez de Arenas Coronado
2024-01-22 21:34 ` Jeff King
2024-01-22 21:45 ` Junio C Hamano [this message]
2024-01-22 21:59 ` Jeff King
2024-01-24 2:58 ` Elijah Newren
2024-01-24 17:06 ` Junio C Hamano
2024-01-24 18:57 ` Jeff King
2024-01-23 5:40 ` Raúl Núñez de Arenas Coronado
2024-01-24 1:09 ` Jeff King
2024-01-24 14:22 ` Raúl Núñez de Arenas Coronado
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=xmqq1qa9rqji.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=raulnac@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.