code review 5673080: doc: update gccgo_contribute.html

doc: update gccgo_contribute.html

[iant, 2012-02-17 06:13:17]

Hello golang-dev@googlegroups.com,

I'd like you to review this change to
https://go.googlecode.com/hg/

[r, 2012-02-17 07:16:19]

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html
File doc/gccgo_contribute.html (right):

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode8
doc/gccgo_contribute.html:8: These are some notes on contributing to the gccgo
frontend for GCC.
what is it called? gccgo? <code>gccgo</code>? GCCGO?
you seem to have chosen gccgo, which is fine but looks odd when GCC is the thing
it's built on.

it's entirely up to you, but tell us how it should be spelled and we'll make
sure to be consistent. and you should be consistent here; there are still a
number of the <code> variants.

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode43
doc/gccgo_contribute.html:43: Changes to these directories always flow from the
master sources to
"master sources" is undefined

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode67
doc/gccgo_contribute.html:67: changes should be made in the main Go repository. 
The files outside
c.f. master sources?

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode85
doc/gccgo_contribute.html:85: main Go repository are run using the DejaGNU
script found in
s/are/is/

[iant, 2012-02-17 14:28:54]

PTAL

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html
File doc/gccgo_contribute.html (right):

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode8
doc/gccgo_contribute.html:8: These are some notes on contributing to the gccgo
frontend for GCC.
On 2012/02/17 07:16:19, r wrote:
> what is it called? gccgo? <code>gccgo</code>? GCCGO?
> you seem to have chosen gccgo, which is fine but looks odd when GCC is the
thing
> it's built on.
> 
> it's entirely up to you, but tell us how it should be spelled and we'll make
> sure to be consistent. and you should be consistent here; there are still a
> number of the <code> variants.

Yeah, I agree it's inconsistent right now.  I'm open to suggestions, but right
now I think the project should be called gccgo (capitalized at the start of a
sentence) and the program, in usage examples or other specific references,
should be called <code>gccgo</code>.  The GCC project is these days usually
called "GCC" rather than "gcc", but I think I would rather write "gccgo" than
"GCCGO".  I cleaned this up in the rest of the doc.

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode43
doc/gccgo_contribute.html:43: Changes to these directories always flow from the
master sources to
On 2012/02/17 07:16:19, r wrote:
> "master sources" is undefined

Done.

http://codereview.appspot.com/5673080/diff/1/doc/gccgo_contribute.html#newcode85
doc/gccgo_contribute.html:85: main Go repository are run using the DejaGNU
script found in
On 2012/02/17 07:16:19, r wrote:
> s/are/is/

Done.

[r, 2012-02-18 06:42:53]

LGTM

[iant, 2012-02-18 19:16:03]

*** Submitted as http://code.google.com/p/go/source/detail?r=a3e2c790db24 ***

doc: update gccgo_contribute.html

R=golang-dev, r
CC=golang-dev
http://codereview.appspot.com/5673080