From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Mon,  2 Dec 2013 09:33:03 -0500
To: 9fans@9fans.net
Message-ID: <07d69aa884813549f2627680ea470392@mikro>
In-Reply-To: <20131202082259.GA18890@dinah>
References: <f1f540c3c271b35b940f50607d11a615@proxima.alt.za>
	<35c5de340bd7283e907593e1ba64569f@gmx.de>
	<20130602193744.GA32587@dinah>
	<CAJSxfmJReiEhfOLexxLBgT-CDQcfxuyVMvvbWfriJBP2XbCHsA@mail.gmail.com>
	<20131202082259.GA18890@dinah>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status)
Topicbox-Message-UUID: 8cc96446-ead8-11e9-9d60-3106f5b1d025

> The Go tree is still in a code freeze but I'll have those
> CLs submitted as soon as it reopens.
>
> Also, we have three months (until the Go 1.3 code freeze) to
> get the Plan 9 port passing all tests on the build dashboard
> or it will have to move outside the main repository:

there is no demotivation in open source as powerful as a threat.

is the threat standing?  that is, if the plan 9 port is broken again
when 1.5 rolls around in just a few more months, does the plan 9
port get booted then, too?

personally, i think a preemtive strike is in order.  a lot of time
has been spent chasing basic broken-with-merge issues, the
rather superfluous libbio macros, the self-inflicted memmove
problem, &c.  those are just recent issues.  given the rate of go
development, i would think this is likely to continue.

- erik