From: rpjday@crashcourse.ca
To: git@vger.kernel.org
Subject: is there a truly compelling rationale for .git/info/exclude?
Date: Fri, 06 Oct 2017 06:14:34 -0400 [thread overview]
Message-ID: <20171006061434.Horde.16MqZ-fejqXm6BLpL7prK1K@crashcourse.ca> (raw)
currently having a discussion with ben straub of "pro git" notoriety,
and he and i seem to agree that there's not much value in registering
ignore patterns in a repo-specific .git/info/exclude file.
on the one hand, the .gitignore files that come with a repo would
represent (in ben's terminology, which i really like) the "intrinsic"
patterns to be ignored that are related to the basic content of the repo.
at the other end, users are certainly welcome to add extra patterns
to be ignored, based purely on the way they work -- perhaps based on
their choice of editor, they might want to exclude *.swp files, or
if working on a Mac, ignore .DS_Store, and so on, using a
core.excludesFile setting.
and in this funny grey area in between, we have .git/info/exclude,
to be used for ... what, exactly? the one argument i've come up with
is the situation where you discover that a repo you've cloned has an
incomplete set of .gitignore patterns, and while you submit a patch
for that to the maintainer, you can temporarily add that pattern
to .git/info/exclude, and as soon as the patch is accepted, you can
toss it.
but even that isn't a really compelling reason. so what's it for?
rday
next reply other threads:[~2017-10-06 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 10:14 rpjday [this message]
2017-10-06 12:13 ` is there a truly compelling rationale for .git/info/exclude? Junio C Hamano
2017-10-06 17:39 ` Robert P. J. Day
2017-10-06 19:23 ` Jonathan Nieder
2017-10-07 21:20 ` brian m. carlson
2017-10-12 23:18 ` Johannes Schindelin
2017-10-12 23:56 ` Jeff King
2017-10-13 7:05 ` Robert P. J. Day
2017-10-06 14:18 ` Kaartic Sivaraam
2017-10-08 8:41 ` Steinar Bang
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171006061434.Horde.16MqZ-fejqXm6BLpL7prK1K@crashcourse.ca \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).