Re: is there a truly compelling rationale for .git/info/exclude?
- From
- Steinar Bang <sb@dod.no>
- Date
- Oct 8, 2017, 08:41 UTC
- Message-ID
- <86efqe3ub1.fsf@dod.no>
- 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