From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Sparr <sparr0@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org
Subject: Re: Lack of system-level excludesFile
Date: Thu, 03 Oct 2024 14:55:29 -0700 [thread overview]
Message-ID: <xmqqh69shmwe.fsf@gitster.g> (raw)
In-Reply-To: <20241003212451.GA12763@coredump.intra.peff.net> (Jeff King's message of "Thu, 3 Oct 2024 17:24:51 -0400")
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 ;-)
prev parent reply other threads:[~2024-10-03 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANp3UNBGd=jiSZyFSAdPjayvgHbP5SF4Dm-uCNwna_H16bRgRA@mail.gmail.com>
2024-10-03 0:23 ` Lack of system-level excludesFile Sparr
2024-10-03 8:15 ` brian m. carlson
2024-10-03 15:39 ` Junio C Hamano
2024-10-03 17:45 ` Sparr
2024-10-03 21:24 ` Jeff King
2024-10-03 21:55 ` Junio C Hamano [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=xmqqh69shmwe.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=sparr0@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 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).