On Sat, 27 May 2017 11:37:54 -0400, Rob Tompkins <chtom...@gmail.com> wrote: > > > > On May 27, 2017, at 11:25 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > On May 27, 2017 7:23 AM, "Bernd Eckenfels" <e...@zusammenkunft.net> wrote: > > > > I vote for a default set optimized for build-related file but allow all > > commiters to include relevant files (Specifically Editor and IDE specific). > > One could set up this locally, but it is a better experience for new > > developers if they use common tools and don't hit a dirty repo. After all a > > few more lines in .gitignore do not hurt... > > > > +1 to IntelliJ, eclipse, mac auto generated files (e.g. .DS_STORE), windows > auto generates files, and any other files that could arbitrarily end up in > the directory. Furthermore, you can override the .gitignore at commit time > with "git commit --force"
+1 to include the "usual IDE suspects" (emacs ~ files anyone?) in the .gitignore, particularly for Commons which may see many "drive by" contributors who don't have their global gitignore perfectly set up. (I don't even have one!) Should we add it to https://commons.apache.org/proper/commons-build-plugin/ or keep the .gitignores drifting per component? -- Stian Soiland-Reyes The University of Manchester http://www.esciencelab.org.uk/ http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
