<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pilif</author><text>I&apos;m of the opinion that artifacts of IDEs an OSes should not be part of a projects .gitignore. After all, different people could be using different environments for development and I really don&apos;t see the need for a projects .gitignore to contain the subset of all possible artifacts.&lt;p&gt;Use .git/info/exclude or a repository independent personal .gitignore for this.&lt;p&gt;The projects file is for files created by running the code or maybe some unavoidable build artifacts happening in all cases (.o files for example)&lt;p&gt;I really hate commits with messages like &quot;updating .gitignore for Joe&apos;s new IDE&quot;</text><parent_chain></parent_chain></comment><story><title>A Collection of Useful .gitignore Templates</title><url>http://github.com/github/gitignore</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>avar</author><text>Some projects like Git itself refuse to add editor droppings like &lt;i&gt;~ and #&lt;/i&gt; to .gitignore. They consider the .gitignore file to be &lt;i&gt;only&lt;/i&gt; for things that the build system produces, e.g. *.o and binaries.&lt;p&gt;If you want to ignore things that your editor adds you should add it in .git/info/excludes, not .gitignore.</text><parent_chain></parent_chain></comment><story><title>A Collection of Useful .gitignore Templates</title><url>http://github.com/github/gitignore</url></story>