From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 14:48:56 -0800 [thread overview]
Message-ID: <20161219224856.GB40372@wopr> (raw)
In-Reply-To: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com>
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
next prev parent reply other threads:[~2016-12-19 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 22:23 sl
2016-12-19 22:48 ` Kurt H Maier [this message]
2016-12-19 22:55 ` [9front] " sl
2016-12-20 1:23 ` kokamoto
2016-12-20 1:30 ` Stanley Lieber
2016-12-20 2:14 ` kokamoto
2016-12-20 2:27 ` sl
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=20161219224856.GB40372@wopr \
--to=khm@sciops.net \
--cc=9front@9front.org \
/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).