Re: Fwd: Unexpected behavior of ls-files command when using --others --exclude-from, and a .gitignore file which resides in a subdirectory

From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Elijah Newren" <newren@gmail.com>,
	"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 16:59:54 -0500	[thread overview]
Message-ID: <20240122215954.GA813833@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq1qa9rqji.fsf@gitster.g>

On Mon, Jan 22, 2024 at 01:45:05PM -0800, Junio C Hamano wrote:

> 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.

Yeah, mostly I was surprised that e750951e74 used as strong a word as
"deprecated".

-Peff