9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go/Inferno toolchain (Was: comment and newline in
Date: Tue, 29 Jun 2010 10:24:08 -0700	[thread overview]
Message-ID: <AANLkTilKt-m5lRSWKPXiPhH-LxDhMJvBAPWkCBDfbDl0@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimXX2a313eMOlHAdzYfCpfr8YYE9-YhEgZPUKOo@mail.gmail.com>

On Mon, Jun 28, 2010 at 3:03 PM, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> On Sat, Jun 26, 2010 at 4:26 AM,  <lucio@proxima.alt.za> 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.  I'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.  You 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....
>
>       -eric

Is the porting process active?

-rob



  reply	other threads:[~2010-06-29 17:24 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
2010-06-28 22:03           ` Eric Van Hensbergen
2010-06-29 17:24             ` Rob Pike [this message]
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=AANLkTilKt-m5lRSWKPXiPhH-LxDhMJvBAPWkCBDfbDl0@mail.gmail.com \
    --to=robpike@gmail.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).