From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from th.inri.net ([216.126.196.42]) by ur; Mon Dec 19 20:30:13 EST 2016 Received: (qmail 78822 invoked from network); 20 Dec 2016 01:30:12 -0000 Received: from mobile-166-175-59-4.mycingular.net (HELO ?10.141.132.105?) (sl@166.175.59.4) by th.inri.net with SMTP; 20 Dec 2016 01:30:12 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: [9front] bugs.9front.org: update file structure From: Stanley Lieber X-Mailer: iPhone Mail (14C92) In-Reply-To: <91ad4a647b02fe6c35f32c258a44c5ba@ci5dell.jitaku.localdomain> Date: Mon, 19 Dec 2016 20:30:11 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <68D78BEB-BD48-45E2-B859-11AFC53C59DB@stanleylieber.com> References: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com> <91ad4a647b02fe6c35f32c258a44c5ba@ci5dell.jitaku.localdomain> To: 9front@9front.org List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: immutable RESTful SVG strategy rich-client generator Kenji, There exists a very rudimentary 9front bug tracker at: http://bugs.9front.org You can submit bugs via e-mail and subscribe to the 9front-bugs mailing list= , where all these submissions are ultimately forwarded. This is all document= ed in the FQA. In my previous post I was talking about modifying the big tracker from its c= urrent functionality to the new functionality I proposed in the message. sl