Bug#847520: please consider naming the new section go, not golang

2018-10-21 Thread Guillem Jover
Hi! On Mon, 2018-02-05 at 08:46:33 +0100, Michael Stapelberg wrote: > Fair enough. Personally, I’m happy with either name. Certainly, “golang” is > used in enough places that people know what is meant. As long as we refer > to the language (e.g. in the section description) by “Go”, I think we > sh

Bug#847520: please consider naming the new section go, not golang

2018-02-04 Thread Michael Stapelberg
Fair enough. Personally, I’m happy with either name. Certainly, “golang” is used in enough places that people know what is meant. As long as we refer to the language (e.g. in the section description) by “Go”, I think we should be good. On Mon, Feb 5, 2018 at 1:46 AM, Guillem Jover wrote: > Hi! >

Bug#847520: please consider naming the new section go, not golang

2018-02-04 Thread Guillem Jover
Hi! On Sun, 2018-02-04 at 23:37:39 +0100, Michael Stapelberg wrote: > Matthias Klose writes: > > Please could you consider using go as new tag name? golang resembles > > too much to one particular implementation name. For other languages > > we have python, not cpython, pypy, jython, we have ja

Bug#847520: please consider naming the new section go, not golang

2018-02-04 Thread Michael Stapelberg
Hi Matthias, Matthias Klose writes: > Please could you consider using go as new tag name? golang resembles too much > to one particular implementation name. For other languages we have python, > not > cpython, pypy, jython, we have java, not openjdk. Indeed, the language is called Go, and gol

Bug#847520: please consider naming the new section go, not golang

2017-11-13 Thread Matthias Klose
Please could you consider using go as new tag name? golang resembles too much to one particular implementation name. For other languages we have python, not cpython, pypy, jython, we have java, not openjdk. Matthias