From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Go/Inferno toolchain (Was: comment and newline in
Date: Sat, 26 Jun 2010 13:00:45 +0200 [thread overview]
Message-ID: <b0fb7026b757e6d25d8d22ea2358e364@proxima.alt.za> (raw)
In-Reply-To: <6b38de346a9fc846a24cf6114d2ad4c7@kw.quanstro.net>
>> My particular concern is to encourage convergence towards a single
>> source distribution rather than divergence as seems to have been the
>> case so far with Plan 9 native, Inferno, p9p and now Go. What I have
> [...]
>> And, obvious sequitur, what would it take to replace Plan 9's "patch"
>> approach with a "codereview" one? It seems to me that everyone might
>> benefit from it.
>
> i suppose it needs saying: bell labs, not to be confused with google, ...
Hard to confuse the two, but it doesn't hurt to clarify. Codereview
is run as an independent operation and would give Bell Labs some
breathing space. Good or bad, that's much more difficult to decide,
but I think that those who might participate in the review process
(and remember that the Go Authors seem to be behind codereview for Go
and we know some of them well) would have Plan 9's best interest at
heart too.
++L
next prev parent reply other threads:[~2010-06-26 11:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 15:35 [9fans] comment and newline in define lucio
[not found] ` <AANLkTilhVWAu8htoIL903rtMK1z9Sw88pSfEASawc5Xi@mail.gmail.com>
2010-06-26 0:50 ` Christopher Nielsen
2010-06-26 0:58 ` erik quanstrom
2010-06-26 4:18 ` Rob Pike
2010-06-26 6:15 ` Christopher Nielsen
2010-06-26 5:19 ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) lucio
2010-06-26 6:46 ` Christopher Nielsen
2010-06-26 9:26 ` [9fans] Go/Inferno toolchain (Was: comment and newline in lucio
2010-06-26 10:34 ` erik quanstrom
2010-06-26 11:00 ` lucio [this message]
2010-06-28 22:03 ` Eric Van Hensbergen
2010-06-29 17:24 ` Rob Pike
2010-06-29 17:31 ` Devon H. O'Dell
2010-06-29 17:36 ` Francisco J Ballesteros
2010-06-29 17:48 ` Francisco J Ballesteros
2010-06-29 18:02 ` Jack Johnson
2010-06-29 18:10 ` Eric Van Hensbergen
2010-06-29 18:12 ` Francisco J Ballesteros
2010-06-29 20:30 ` Eric Van Hensbergen
2010-06-29 18:32 ` erik quanstrom
2010-06-29 20:45 ` Eric Van Hensbergen
2010-06-29 20:52 ` erik quanstrom
2010-06-29 21:03 ` ron minnich
2010-06-29 21:36 ` Steve Simon
2010-06-29 21:54 ` Charles Forsyth
2010-06-30 9:25 ` Lucio De Re
2010-06-29 22:35 ` cinap_lenrek
2010-06-29 23:00 ` Russ Cox
2010-06-30 8:17 ` Lucio De Re
2010-06-29 21:15 ` Devon H. O'Dell
2010-06-29 21:27 ` ron minnich
2010-06-26 7:37 ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) Ethan Grammatikidis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0fb7026b757e6d25d8d22ea2358e364@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).