code review 8871043: doc: fix another broken link

doc: fix another broken link

Fixes issue 5316

[bradfitz, 2013-04-19 17:04:26]

Hello golang-dev@googlegroups.com,

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

[r, 2013-04-19 17:42:46]

LGTM

cool comment too

[minux1, 2013-04-19 18:40:35]

do we need to document godoc's new note mechanism?

https://codereview.appspot.com/8871043/diff/5001/doc/articles/godoc_documenti...
File doc/articles/godoc_documenting_go_code.html (right):

https://codereview.appspot.com/8871043/diff/5001/doc/articles/godoc_documenti...
doc/articles/godoc_documenting_go_code.html:82: godoc's output, with one notable
exception. Top-level comments that begin with
i think BUG might not be the sole exception now.

as there is -note option that control godoc which notes
to display (BUG is the default value).

[r, 2013-04-19 18:50:50]

the new note mechanism is mentioned briefly in the go1.1 release notes.

i don't believe the full story is a priority here, and it's likely to
change after go1.1. anyway.

[minux1, 2013-04-19 18:56:56]

On Sat, Apr 20, 2013 at 2:50 AM, Rob Pike <r@golang.org> wrote:

> the new note mechanism is mentioned briefly in the go1.1 release notes.
>
> i don't believe the full story is a priority here, and it's likely to
> change after go1.1. anyway.
>
sure. LGTM.

This BUG is very unlikely to disappear, so we don't need update the
section again, i hope.

[bradfitz, 2013-04-19 19:00:45]

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

doc: fix another broken link

Fixes issue 5316

R=golang-dev, r, minux.ma
CC=golang-dev
https://codereview.appspot.com/8871043