From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <464534aea8c7fffa248a1368c41acb55@proxima.alt.za> Date: Tue, 29 Jun 2010 13:31:15 -0400 Message-ID: From: "Devon H. O'Dell" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Go/Inferno toolchain (Was: comment and newline in Topicbox-Message-UUID: 3907b814-ead6-11e9-9d60-3106f5b1d025 2010/6/29 Rob Pike : > On Mon, Jun 28, 2010 at 3:03 PM, Eric Van Hensbergen w= rote: >> On Sat, Jun 26, 2010 at 4:26 AM, =A0 wrote: >>>> but I can dig >>>> them up, clean them up, and share them, >>> >>> 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 >>> chosen to do, ill-advised as it may be, is to set up a mercurial >>> repository to re-distribute hacked Go sources that mostly contain >>> harmless changes that make it possible to compile the Go sources and >>> specifically the development toolchain with the Plan 9 toolchain. =A0I'= m >>> presently trying to bring the work I did last year into this >>> repository and at the same time keep track of the Go release. >>> >> >> I've had a composite repo of previous attempts (well, Sape's previous >> attempt) at doing this (for some time) at: >> http://code.google.com/p/go-plan9/ >> >> I'm happy to add anyone to the committer/admin list, although my >> preference is to keep the main branch in sync with go and have folks >> attempts at conversion in sub-branches. =A0You are of course welcome to >> maintain your own repo with your own effort, I just figured if >> everyone had a common place to see what approaches people were using >> we might get there faster.... >> >> =A0 =A0 =A0 -eric > > Is the porting process active? I haven't had time, but have made promises. I'll start tonight. --dho > -rob > >