From mboxrd@z Thu Jan 1 00:00:00 1970 To: <9fans@9fans.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 12 Nov 2010 03:07:04 -0600 From: EBo In-Reply-To: References: <75ea74312ad96f76de8cd4b3291ffb1d@brasstown.quanstro.net> <1e4bfd86eef85bbf4434f8ef22b6fed7@plug.quanstro.net> <948e9cbd967366d058ac8a033ce93f5f@plug.quanstro.net> <53acf6ebfa4f01bbe09d6ed494ef68b1@plug.quanstro.net> Message-ID: <9a9e0cc30cdb51a02aa6a8ddc78432b8@swcp.com> User-Agent: RoundCube Webmail/0.4-trunk Subject: Re: [9fans] p9p factotum available for plan 9 Topicbox-Message-UUID: 7ac23112-ead6-11e9-9d60-3106f5b1d025 > 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. EBo --