From: Steinar Bang <sb@dod.no>
To: git@vger.kernel.org
Subject: Re: is there a truly compelling rationale for .git/info/exclude?
Date: Sun, 08 Oct 2017 10:41:54 +0200 [thread overview]
Message-ID: <86efqe3ub1.fsf@dod.no> (raw)
In-Reply-To: 20171006061434.Horde.16MqZ-fejqXm6BLpL7prK1K@crashcourse.ca
>>>>> rpjday@crashcourse.ca:
> but even that isn't a really compelling reason. so what's it for?
I use it to ignore stuff in my git-versioned home directory.
Every time I use a new program and it creates a config file or a config
directory, it shows up as clutter in magit in my git versioned home
directory.
I started with putting the stuff to be ignored in .gitignore, but since
I run different stuff on different machines and on different OSes,
.gitignore started to contain irrelevant stuff (ignoring a stuff from a
program that was run once and then never again, ignoring stuff on one
machine that maybe should not be ignored on a different machine), and
then I figured it was much simpler to just ignore stuff repo-locally in
.git/info/exclude
prev parent reply other threads:[~2017-10-08 8:42 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
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 [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
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=86efqe3ub1.fsf@dod.no \
--to=sb@dod.no \
--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).