From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] The Web9 Project
Date: Sun, 9 Sep 2007 11:44:35 +0200 [thread overview]
Message-ID: <8ccc8ba40709090244r4f6acf88o9c245287ec3e3fd0@mail.gmail.com> (raw)
In-Reply-To: <f158dc670709082046h15b168cev687fc212564b90a8@mail.gmail.com>
On 9/9/07, Latchesar Ionkov <lucho@gmx.net> wrote:
> We already agreed on a solution. Nobody is interested in implementing it.
>
Well, I started indeed. But then noticed that I needed just a
different protocol and
went for it. I may try again in the future with what I learned from
our current attempt.
next prev parent reply other threads:[~2007-09-09 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE662DC3-5A6C-45BB-8623-A569338F4C46@kix.in>
2007-09-08 12:39 ` Enrico Weigelt
2007-09-08 19:38 ` Anant Narayanan
2007-09-08 15:45 ` Skip Tavakkolian
2007-09-08 19:46 ` Anant Narayanan
2007-09-08 20:15 ` Uriel
2007-09-09 3:46 ` Latchesar Ionkov
2007-09-09 9:44 ` Francisco J Ballesteros [this message]
2007-09-09 11:55 ` erik quanstrom
2007-09-09 12:03 ` Francisco J Ballesteros
2007-09-09 12:18 ` erik quanstrom
2007-09-09 12:52 ` Francisco J Ballesteros
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=8ccc8ba40709090244r4f6acf88o9c245287ec3e3fd0@mail.gmail.com \
--to=nemo@lsub.org \
--cc=9fans@cse.psu.edu \
/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).