From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Sparr <sparr0@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Lack of system-level excludesFile
Date: Thu, 3 Oct 2024 08:15:33 +0000 [thread overview]
Message-ID: <Zv5SpewqUmlvhOl-@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CANp3UNCXqLJmAj2Vc7jB+i9qRjfKzrri_Mr9VvG4J5tUR-1HeQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
On 2024-10-03 at 00:23:17, Sparr wrote:
> Was the decision to not allow or implement such a file intentional, or
> is it just an emergent property of the way the config system works and
> how core.excludesFile was implemented? Would an implementation of a
> new feature supporting this sort of thing be worth discussing?
I wasn't part of the project when the exclude functionality was
implemented, so I can't say what the intent was, but I will note that
even CVS had ignore files. My guess is that it wasn't seen as something
useful to implement, so nobody implemented it, but I think your argument
for doing so isn't bad.
I'll just note that typically I ignore things in the global include
which are likely to affect the environment I use, including my editor
and operating system. So when I was tutoring an Emacs user, we
configured his machine to ignore `*~`, since his editor creates backup
files, and likewise, if I were still using macOS, I'd ignore
`.DS_Store`.
So basically, I think such a feature could be useful, but I also don't
see it as immediately necessary because the global (per-user) file is
also generally useful for this if the user is aware enough to know it
exists (which I admit they might not be). One thing I would request is
that if you add this, you add an appropriate var to `git var` so that
people can find the location, which is important because different
versions of Git (say, Apple's vs. Homebrew's) may install the system
configuration in different locations.
--
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2024-10-03 8:15 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 [this message]
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
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=Zv5SpewqUmlvhOl-@tapette.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--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).