From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] rc exec error behaviour
Date: Mon, 1 Feb 2016 17:01:01 +0000 [thread overview]
Message-ID: <13e6d9a8361b785329ae11b7cbd44b0e@hamnavoe.com> (raw)
In-Reply-To: <b01fedd1c007382ef060c0e7b8c02ccc@proxima.alt.za>
> Richard Miller is contributing a lot of great stuff to Go for plan9/arm.
Thank you, but mostly I've just updated and titivated the previous
work from Lucio and Gorka, to the state where it should pass the
codereview and does pass all the go1.6 tests (with *ncpu=1).
For multicore I am still chasing down some bugs in Plan 9 (and not
only on arm) which seem to be flushed out by the particularly brutal
go test suite.
next prev parent reply other threads:[~2016-02-01 17:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 16:31 cinap_lenrek
2016-01-31 1:16 ` Prof Brucee
2016-01-31 4:20 ` lucio
2016-01-31 6:58 ` Skip Tavakkolian
2016-02-01 0:52 ` Sean Hinchee
2016-02-01 4:06 ` erik quanstrom
2016-02-01 4:29 ` lucio
2016-02-01 17:01 ` Richard Miller [this message]
2016-02-01 18:35 ` lucio
2016-02-02 1:29 ` Prof Brucee
2016-02-02 10:53 ` Richard Miller
2016-02-02 12:36 ` Aram Hăvărneanu
2016-02-02 12:53 ` hiro
2016-02-02 13:23 ` David du Colombier
2016-02-02 15:46 ` lucio
2016-02-02 16:02 ` David du Colombier
2016-02-02 16:46 ` Skip Tavakkolian
2016-02-02 16:52 ` Skip Tavakkolian
2016-02-02 17:11 ` sl
2016-02-03 0:37 ` Sean Hinchee
2016-02-03 0:48 ` Kurt H Maier
2016-02-02 17:24 ` sl
2016-02-02 17:33 ` Wes Kussmaul
2016-02-01 20:33 ` [9fans] plan9/arm in Go 1.7? (was: rc exec error behaviour) Skip Tavakkolian
2016-02-01 20:45 ` David du Colombier
2016-02-02 4:16 ` [9fans] rc exec error behaviour Lyndon Nerenberg
2016-02-02 4:21 ` Prof Brucee
2016-02-02 4:24 ` Lyndon Nerenberg
2016-02-22 0:19 ` erik quanstrom
2016-02-03 0:48 sl
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=13e6d9a8361b785329ae11b7cbd44b0e@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).