From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] ot: pascal rides again?
Date: Mon, 25 May 2015 07:39:23 +0200 [thread overview]
Message-ID: <ac69e0b7da3bd63ae82024eed729cc50@proxima.alt.za> (raw)
In-Reply-To: <CA+db=n0YS7CNbTXu93+S_y+6erCCbFBSu2ktu=+7-1=CRPBzeA@mail.gmail.com>
> (i.e. you don't need ~65 pages of style guide just to tell you how to
> write acceptable code.)
I think it's wasteful to defend Go. Let history do that...
Lucio.
next prev parent reply other threads:[~2015-05-25 5:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 15:53 erik quanstrom
2015-05-23 16:17 ` Eduardo Alvarez
2015-05-23 16:26 ` Aram Hăvărneanu
2015-05-23 18:14 ` C Cirello
2015-05-23 18:25 ` Ryan Gonzalez
2015-05-24 15:55 ` erik quanstrom
2015-05-24 16:19 ` Devon H. O'Dell
2015-05-24 17:02 ` Aram Hăvărneanu
2015-05-24 17:53 ` Ryan Gonzalez
2015-05-24 17:50 ` Ryan Gonzalez
2015-05-24 19:00 ` Bakul Shah
2015-05-24 19:36 ` Ryan Gonzalez
2015-05-24 21:25 ` minux
2015-05-25 1:26 ` C Cirello
2015-05-25 5:39 ` lucio [this message]
2015-05-25 7:59 ` Bakul Shah
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=ac69e0b7da3bd63ae82024eed729cc50@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).