Are we talking about only the Maven profile or also about the Java profile. I find that one overly eager and why does it contain BlueJ IDE (only)?
Gruss Bernd -- http://bernd.eckenfels.net ________________________________ From: sebb <seb...@gmail.com> Sent: Monday, June 5, 2017 5:09:18 PM To: Commons Developers List Subject: Re: [all] Should our gitignore files contain only build-related entries? On 5 June 2017 at 11:20, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > > I usually only use what gibo [1] generates. I don’t put editor specific > entries into .gitignore for my personal projects. This stuff should go into > your personal gitignore. If developers don’t know about global gitignore we > should educate them instead of promoting non-sense project setups. +1 > Regards, > Benedikt > > [1] https://github.com/simonwhitaker/gibo > >> Am 01.06.2017 um 19:09 schrieb Gary Gregory <garydgreg...@gmail.com>: >> >> If we do not have per component .gitignore files, then we better have clear >> instructions front and center on how to set up Git for what we expect. >> >> Gary >> >> On Wed, May 31, 2017 at 2:04 AM, Amey Jadiye <ameyjad...@gmail.com> wrote: >> >>> Hi, >>> >>> I think easier way to have all ignorable extensions and directories in >>> .gitignore and same have to be replicated in global gitignore from all >>> other Commons projects. Commons is always having short fixes and >>> improvements , people tend to fork>work>PR>delete repo on local pc. >>> Instructions should be in UsingGIT and CONTRIBUTING.md but not sure people >>> will follow everything. Ignores already present in .gitignore of each >>> project makes everything painles. >>> >>> Regards, >>> Amey >>> >>> On Sat, May 27, 2017, 7:03 PM Bruno P. Kinoshita >>> <brunodepau...@yahoo.com.br.invalid> wrote: >>> >>>> Hi, >>>> >>>> [collections] recently received a pull request [1] to add VIM files to >>> the >>>> gitignore file. Its currently gitignore contains only a few entries for >>>> Eclipse ([lang] has more entries for Eclipse). >>>> >>>> I remember asking something similar, and learning about the global >>>> gitignore. But besides that, in the same thread, Benedikt suggested >>> having >>>> only build files ignored in our gitignore files [2], which I think is a >>>> good idea. Our components do not follow any rule for gitignore files I >>>> think. I normally check [lang] when I need to add a .gitignore to a new >>>> computer, but just realized [text] and [lang] gitignore files differ >>>> ([lang] has a .checkstyle file under the Eclipse ignored files). >>>> >>>> >>>> I'm okay merging the pull request for [collections], but then we may also >>>> add the remaining entries from [lang] there... except this pull request >>>> adds *.swp which is missing from [lang]. So should we add it there too? >>>> >>>> Some days ago I used NetBeans to test a generics suppress warning message >>>> [3], but we may have developers using it as main IDE too. Would it be all >>>> right to merge pull requests for it too? Or for files generated by >>> plug-ins >>>> for Eclipse/IntelliJ/etc? >>>> What about 1) leaving only files generated by our build tools, 2) add a >>>> comment to the .gitignore file describing how it works with links, 3) >>> add a >>>> comment to >>>> https://wiki.apache.org/commons/UsingGIT and/or to the CONTRIBUTING.md >>>> perhaps with a sample global gitignore file? >>>> >>>> Cheers >>>> Bruno >>>> >>>> [1] https://github.com/apache/commons-collections/pull/21 >>>> [2] >>>> http://markmail.org/message/yvflc6kxgjalhldx?q=global+ >>> gitignore+list:org%2Eapache%2Ecommons%2Edev#query:global% >>> 20gitignore%20list%3Aorg.apache.commons.dev+page:1+mid: >>> ioex63sxnf6culwb+state:results >>>> [3] https://github.com/apache/commons-collections/pull/17 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >>>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
