From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p factotum available for plan 9
Date: Fri, 12 Nov 2010 07:12:42 -0800 [thread overview]
Message-ID: <AANLkTingarCaqss7sueEbOq7H_qB=cboXboarTv_boAF@mail.gmail.com> (raw)
In-Reply-To: <9a9e0cc30cdb51a02aa6a8ddc78432b8@swcp.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Fri, Nov 12, 2010 at 1:07 AM, EBo <ebo@sandien.com> wrote:
> Does anyone use 9P2000.u anymore?
>> Can we just remove it from the p9p tree?
>>
>
> Last summer when I was banging my head against the bug in alloctree I got
> it all to work when I removed 9P2000.u and some other stuff from
> lib9p/srv.c. At that time I got a comment back that the patches I proposed
> would likely not be accepted, in part because I removed the 9P2000.u code...
>
> If there are no objections to removing 9P2000.u, I can tell you that
> migrating p9p's srv.c code back to Plan 9's version does in fact fix the
> bugs in Tree. I was simply not sure how many of the changes had to be
> reverted to make alloctree work properly.
>
>
>
It seems like a good idea to removing .u. I think I can add .u back to some
other 9P implementations I have if I want it.
Dave
> EBo --
>
>
>
[-- Attachment #2: Type: text/html, Size: 1505 bytes --]
next prev parent reply other threads:[~2010-11-12 15:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 21:13 erik quanstrom
2010-11-09 3:37 ` erik quanstrom
2010-11-09 17:41 ` David Leimbach
2010-11-09 17:51 ` erik quanstrom
2010-11-10 0:37 ` erik quanstrom
2010-11-10 1:49 ` Russ Cox
2010-11-10 6:46 ` erik quanstrom
2010-11-10 14:31 ` Russ Cox
2010-11-12 3:35 ` Noah Evans
2010-11-12 5:34 ` erik quanstrom
2010-11-12 5:46 ` Noah Evans
2010-11-12 6:03 ` Noah Evans
2010-11-12 6:19 ` Russ Cox
2010-11-12 6:25 ` Noah Evans
2010-11-12 9:07 ` EBo
2010-11-12 15:12 ` David Leimbach [this message]
2010-11-12 15:19 ` Eric Van Hensbergen
2010-11-12 15:35 ` erik quanstrom
2010-11-12 15:55 ` Russ Cox
2010-11-12 16:22 ` Eric Van Hensbergen
2010-11-12 19:55 ` ron minnich
2010-11-12 20:23 ` erik quanstrom
2010-11-12 20:31 ` Eric Van Hensbergen
2010-11-12 20:37 ` ron minnich
2010-11-12 20:30 ` Eric Van Hensbergen
2010-11-12 20:41 ` ron minnich
2010-11-12 22:15 ` Eric Van Hensbergen
2010-11-12 22:20 ` ron minnich
2010-11-12 22:36 ` Russ Cox
2010-11-13 8:31 ` tlaronde
2010-11-13 23:42 ` Dave Eckhardt
2010-11-14 22:49 ` Nathaniel W Filardo
2010-11-15 16:22 ` erik quanstrom
2010-11-15 17:40 ` Nathaniel W Filardo
2010-11-15 17:50 ` John Floren
2010-11-12 21:12 ` Russ Cox
2010-11-09 18:08 ` yy
2010-11-09 19:17 ` Bakul Shah
2010-11-09 19:27 ` Russ Cox
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='AANLkTingarCaqss7sueEbOq7H_qB=cboXboarTv_boAF@mail.gmail.com' \
--to=leimy2k@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).