git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Lack of system-level excludesFile

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 3, 2024, 21:55 UTC
Message-ID
<xmqqh69shmwe.fsf@gitster.g>
In-Reply-To
<20241003212451.GA12763@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
> PS If you want to get really wild, consider this: the exclude/ignore
>    feature is really just a proper subset of the attributes system that
>    came later. If we were designing today, we could ditch .gitignore
>    entirely in favor of a special "ignored" attribute,
Yes, this was brought up in the past a few times.

Both the exclude stack (in dir.c) and attr stack (in attr.c) use a similar approach to optimize the accesses to the data for callers that traverse the paths in-order and ask if something is ignored (or has this attribute) for each of the paths they encounter, so their performance characteristics might be similar. It certainly is a tempting thought and indeed is a big project, especially if you want to keep some sort of backward compatibility ;-)

Previous: Jeff King
Message 6 of 6 in “Lack of system-level excludesFile”
  1. SparrOct 3, 2024
  2. brian m. carlsonOct 3, 2024
  3. Junio C HamanoOct 3, 2024
  4. SparrOct 3, 2024
  5. Jeff KingOct 3, 2024
  6. Junio C HamanoOct 3, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.