[all] Should our gitignore files contain only build-related entries?

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

[all] Should our gitignore files contain only build-related entries?

Bruno P. Kinoshita-3
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Bernd Eckenfels
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...

Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
From: Bruno P. Kinoshita <[hidden email]>
Sent: Saturday, May 27, 2017 3:29:22 PM
To: Commons Developers List
Subject: [all] Should our gitignore files contain only build-related entries?

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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

garydgregory
On May 27, 2017 7:23 AM, "Bernd Eckenfels" <[hidden email]> 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...


Sounds reasonable to me.

Gary


Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
From: Bruno P. Kinoshita <[hidden email]>
Sent: Saturday, May 27, 2017 3:29:22 PM
To: Commons Developers List
Subject: [all] Should our gitignore files contain only build-related
entries?

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: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Rob Tompkins


> On May 27, 2017, at 11:25 AM, Gary Gregory <[hidden email]> wrote:
>
> On May 27, 2017 7:23 AM, "Bernd Eckenfels" <[hidden email]> 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"

-Rob

>
> Sounds reasonable to me.
>
> Gary
>
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> From: Bruno P. Kinoshita <[hidden email]>
> Sent: Saturday, May 27, 2017 3:29:22 PM
> To: Commons Developers List
> Subject: [all] Should our gitignore files contain only build-related
> entries?
>
> 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: [hidden email]
> For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Stian Soiland-Reyes
On Sat, 27 May 2017 11:37:54 -0400, Rob Tompkins <[hidden email]> wrote:

>
>
> > On May 27, 2017, at 11:25 AM, Gary Gregory <[hidden email]> wrote:
> >
> > On May 27, 2017 7:23 AM, "Bernd Eckenfels" <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Jörg Schaible-5
In reply to this post by Bruno P. Kinoshita-3
Hi Bruno,

personally I use normally only two entries:

================== %< =================
.*
target
================== %< =================

Which implies that I have to force the addition of .gitignore and
.gitattributes files.

Cheers,
Jörg


Bruno P. Kinoshita 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Amey Jadiye
In reply to this post by Bruno P. Kinoshita-3
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
<[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

garydgregory
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 <[hidden email]> 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
> <[hidden email]> 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Benedikt Ritter-4
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.

Regards,
Benedikt

[1] https://github.com/simonwhitaker/gibo

> Am 01.06.2017 um 19:09 schrieb Gary Gregory <[hidden email]>:
>
> 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 <[hidden email]> 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
>> <[hidden email]> 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: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

sebb-2-2
On 5 June 2017 at 11:20, Benedikt Ritter <[hidden email]> 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 <[hidden email]>:
>>
>> 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 <[hidden email]> 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
>>> <[hidden email]> 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: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Bernd Eckenfels
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 <[hidden email]>
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 <[hidden email]> 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 <[hidden email]>:
>>
>> 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 <[hidden email]> 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
>>> <[hidden email]> 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: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Bruno P. Kinoshita-3
In reply to this post by sebb-2-2
I can understand trying to make it easier for people to contribute too, but I still prefer to have a more IDE agnostic set up, with build-only files in the .gitignore file, and a global exclusion list. But I think we didn't reach a consensus here, so guess we will just keep the per project setting, and merge the pull requests as they come in and try to keep things as concise as possible.
Cheers
Bruno

      From: sebb <[hidden email]>
 To: Commons Developers List <[hidden email]>
 Sent: Tuesday, 6 June 2017 3:09 AM
 Subject: Re: [all] Should our gitignore files contain only build-related entries?
   
On 5 June 2017 at 11:20, Benedikt Ritter <[hidden email]> 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 <[hidden email]>:
>>
>> 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 <[hidden email]> 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
>>> <[hidden email]> 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: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


   
Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Benedikt Ritter-4
In reply to this post by Bernd Eckenfels
Hello Bernd,

> Am 05.06.2017 um 18:47 schrieb Bernd Eckenfels <[hidden email]>:
>
> 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)?

What are you referring to with „Maven profile“ and „Java profile“?

Cheers,
Benedikt

>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> From: sebb <[hidden email]>
> 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 <[hidden email]> 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 <[hidden email]>:
>>>
>>> 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 <[hidden email]> 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
>>>> <[hidden email]> 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: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Matt Sicker
It might be useful to document a helpful starter .gitignore_global for
users. I tend to set those up and forget about them.

On 6 June 2017 at 06:50, Benedikt Ritter <[hidden email]> wrote:

> Hello Bernd,
>
> > Am 05.06.2017 um 18:47 schrieb Bernd Eckenfels <[hidden email]>:
> >
> > 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)?
>
> What are you referring to with „Maven profile“ and „Java profile“?
>
> Cheers,
> Benedikt
>
> >
> > Gruss
> > Bernd
> > --
> > http://bernd.eckenfels.net
> > ________________________________
> > From: sebb <[hidden email]>
> > 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 <[hidden email]> 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 <[hidden email]>:
> >>>
> >>> 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 <[hidden email]>
> 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
> >>>> <[hidden email]> 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: [hidden email]
> >>>>> For additional commands, e-mail: [hidden email]
> >>>>>
> >>>>>
> >>>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Matt Sicker <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

sebb-2-2
On 6 June 2017 at 15:49, Matt Sicker <[hidden email]> wrote:
> It might be useful to document a helpful starter .gitignore_global for
> users. I tend to set those up and forget about them.

+1

That sounds like a good addition to the Wiki

There is:

https://wiki.apache.org/commons/UsingGIT

That is quite long already, so a new page (linked from it) might be better.

> On 6 June 2017 at 06:50, Benedikt Ritter <[hidden email]> wrote:
>
>> Hello Bernd,
>>
>> > Am 05.06.2017 um 18:47 schrieb Bernd Eckenfels <[hidden email]>:
>> >
>> > 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)?
>>
>> What are you referring to with „Maven profile“ and „Java profile“?
>>
>> Cheers,
>> Benedikt
>>
>> >
>> > Gruss
>> > Bernd
>> > --
>> > http://bernd.eckenfels.net
>> > ________________________________
>> > From: sebb <[hidden email]>
>> > 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 <[hidden email]> 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 <[hidden email]>:
>> >>>
>> >>> 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 <[hidden email]>
>> 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
>> >>>> <[hidden email]> 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: [hidden email]
>> >>>>> For additional commands, e-mail: [hidden email]
>> >>>>>
>> >>>>>
>> >>>>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>
> --
> Matt Sicker <[hidden email]>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

Bernd Eckenfels
In reply to this post by Benedikt Ritter-4
GIBo uses the Github profiles:
https://github.com/github/gitignore/blob/master/Java.gitignore
https://github.com/github/gitignore/blob/master/Maven.gitignore

Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
From: Benedikt Ritter <[hidden email]>
Sent: Tuesday, June 6, 2017 1:50:14 PM
To: Commons Developers List
Subject: Re: [all] Should our gitignore files contain only build-related entries?

Hello Bernd,

> Am 05.06.2017 um 18:47 schrieb Bernd Eckenfels <[hidden email]>:
>
> 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)?

What are you referring to with „Maven profile“ and „Java profile“?

Cheers,
Benedikt

>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> From: sebb <[hidden email]>
> 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 <[hidden email]> 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 <[hidden email]>:
>>>
>>> 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 <[hidden email]> 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
>>>> <[hidden email]> 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: [hidden email]
>>>>> For additional commands, e-mail: [hidden email]
>>>>>
>>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [all] Should our gitignore files contain only build-related entries?

sebb-2-2
On 6 June 2017 at 22:09, Bernd Eckenfels <[hidden email]> wrote:
> GIBo uses the Github profiles:
> https://github.com/github/gitignore/blob/master/Java.gitignore

At least some of those may cause problems for Compress test data ...

> https://github.com/github/gitignore/blob/master/Maven.gitignore
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
> ________________________________
> From: Benedikt Ritter <[hidden email]>
> Sent: Tuesday, June 6, 2017 1:50:14 PM
> To: Commons Developers List
> Subject: Re: [all] Should our gitignore files contain only build-related entries?
>
> Hello Bernd,
>
>> Am 05.06.2017 um 18:47 schrieb Bernd Eckenfels <[hidden email]>:
>>
>> 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)?
>
> What are you referring to with „Maven profile“ and „Java profile“?
>
> Cheers,
> Benedikt
>
>>
>> Gruss
>> Bernd
>> --
>> http://bernd.eckenfels.net
>> ________________________________
>> From: sebb <[hidden email]>
>> 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 <[hidden email]> 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 <[hidden email]>:
>>>>
>>>> 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 <[hidden email]> 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
>>>>> <[hidden email]> 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: [hidden email]
>>>>>> For additional commands, e-mail: [hidden email]
>>>>>>
>>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]