[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    Re: [all] Should our gitignore files contain only build-related entries?
From:       Amey Jadiye <ameyjadiye () gmail ! com>
Date:       2017-05-31 9:04:43
Message-ID: CAPUUeo=DkJLu+7UWRTqy2nqSmbSk23MnDBaSYMeR73opco-Uvw () mail ! gmail ! com
[Download RAW message or body]


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
<brunodepaulak@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%2E \
> commons%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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> 



[prev in list] [next in list] [prev in thread] [next in thread]