From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] PUSH sources for Plan 9
Date: Wed, 26 Jan 2011 18:52:01 -0800 [thread overview]
Message-ID: <AANLkTi=cnvb5LGv-f4-qie8LcbZnXZtDS=fO-jnEXMr=@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=vdExRjUSTd0+25p-gq2cigwiKfQHU=Oa9vvJd@mail.gmail.com>
Yes, I've seen this. This is the port to Plan 9 Ports.
I would like the code for Plan 9. I imagine reproducing
will make things uglier than the original.
On Wed, Jan 26, 2011 at 5:48 PM, Jacob Todd <jaketodd422@gmail.com> wrote:
> http://code.google.com/p/push/
>
>
next prev parent reply other threads:[~2011-01-27 2:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 1:42 Akshat Kumar
2011-01-27 1:48 ` Jacob Todd
2011-01-27 2:52 ` Akshat Kumar [this message]
2011-01-27 3:22 ` Eric Van Hensbergen
2011-01-27 9:08 ` Akshat Kumar
2011-01-27 9:20 ` Anthony Sorace
2011-01-27 10:30 ` Noah Evans
2011-01-29 20:31 ` Akshat Kumar
2011-01-29 22:32 ` Noah Evans
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='AANLkTi=cnvb5LGv-f4-qie8LcbZnXZtDS=fO-jnEXMr=@mail.gmail.com' \
--to=akumar@mail.nanosouffle.net \
--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).