From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ur; Mon Dec 19 17:48:59 EST 2016 Received: (qmail 51316 invoked by uid 1001); 19 Dec 2016 22:48:56 -0000 Date: Mon, 19 Dec 2016 14:48:56 -0800 From: Kurt H Maier To: 9front@9front.org Subject: Re: [9front] bugs.9front.org: update file structure Message-ID: <20161219224856.GB40372@wopr> Mail-Followup-To: 9front@9front.org References: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extended mobile AJAX persistence element framework-oriented manager On Mon, Dec 19, 2016 at 05:23:58PM -0500, sl@stanleylieber.com wrote: > I am unhappy with the way user input is currently mangled. I am > working on a slight overhaul of the way submitting a bug works, and > the way files are stored once a bug is submitted. > > Proposed: > > - Save the entire original message in bugname/mbox/filename. filename > is an mdir file, which is suitable for opening with either > upas or nupas (upas just treats it as an mbox that contains > one message). > - bugs/close will then reply to the saved message, cc: bugs@9front.org > and the original submitter. All relevant links to the bug > (/n/bugs/closed/bugname, etc.) will be automatically added > to the message. > > Pros: > - This will preserve attachments and make replying much easier. > > Cons: > - No mechanism has yet been invented for closing a bug via e-mail. > However, this is a step towards that goal. > > sl I have no objections to this proposal, but I'd like for people to spitball methods by which we might accomplish my goal: I'd like replies to a ML post to be included in the bug page. Does the existing mailing list software handle In-Reply-To or References headers? Can we leverage that to do grouping? One mbox/mdir per bug would be optimal. khm