From: sl@stanleylieber.com
To: 9front@9front.org
Subject: bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 17:23:58 -0500 [thread overview]
Message-ID: <4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com> (raw)
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
next reply other threads:[~2016-12-19 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 22:23 sl [this message]
2016-12-19 22:48 ` [9front] " Kurt H Maier
2016-12-19 22:55 ` 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=4706ccfef7309d2e1a2579ddb816eb9f@pav1.example.com \
--to=sl@stanleylieber.com \
--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).