From: Junio C Hamano <gitster@pobox.com>
To: rpjday@crashcourse.ca
Cc: git@vger.kernel.org
Subject: Re: is there a truly compelling rationale for .git/info/exclude?
Date: Fri, 06 Oct 2017 21:13:57 +0900 [thread overview]
Message-ID: <xmqqmv54v5h6.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171006061434.Horde.16MqZ-fejqXm6BLpL7prK1K@crashcourse.ca> (rpjday@crashcourse.ca's message of "Fri, 06 Oct 2017 06:14:34 -0400")
rpjday@crashcourse.ca writes:
> 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.
This is primarily why .git/info/exclude exists. A user who does not
use the same set of tools to work on different projects may not be
able to use ~/.gitconfig with core.excludesFile pointing at a single
place that applies to _all_ repositories the user touches.
Also, core.excludesFile came a lot later than in-project and
in-repository exclude list, IIRC.
Don't waste time by seeking a "compelling" reason. A mere "this is
the most expedite way to gain convenience" back when something was
introduced could be an answer, and it is way too late to complain
about such a choice anyway.
next prev parent reply other threads:[~2017-10-06 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 10:14 is there a truly compelling rationale for .git/info/exclude? rpjday
2017-10-06 12:13 ` Junio C Hamano [this message]
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=xmqqmv54v5h6.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).