* bugs.9front.org: update file structure
@ 2016-12-19 22:23 sl
2016-12-19 22:48 ` [9front] " Kurt H Maier
2016-12-20 1:23 ` kokamoto
0 siblings, 2 replies; 7+ messages in thread
From: sl @ 2016-12-19 22:23 UTC (permalink / raw)
To: 9front
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9front] bugs.9front.org: update file structure
2016-12-19 22:23 bugs.9front.org: update file structure sl
@ 2016-12-19 22:48 ` Kurt H Maier
2016-12-19 22:55 ` sl
2016-12-20 1:23 ` kokamoto
1 sibling, 1 reply; 7+ messages in thread
From: Kurt H Maier @ 2016-12-19 22:48 UTC (permalink / raw)
To: 9front
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9front] bugs.9front.org: update file structure
2016-12-19 22:48 ` [9front] " Kurt H Maier
@ 2016-12-19 22:55 ` sl
0 siblings, 0 replies; 7+ messages in thread
From: sl @ 2016-12-19 22:55 UTC (permalink / raw)
To: 9front
> 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.
I would like that too. (See below.)
This could be implemented in the pipeto for 9front-bugs.
> Does the existing
> mailing list software handle In-Reply-To or References headers?
It does not.
But: The 9front-bugs and/or 9front-bugs-open pipeto scripts can do
anything we tell them to. We could grep incoming messages for headers
and act accordingly.
> One mbox/mdir per bug would be optimal.
That's the plan.
However: Multiple mdir messages in the bugname/mbox/ directory would
break (or at least, irritate) backwards compatability with upas.
sl
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9front] bugs.9front.org: update file structure
2016-12-19 22:23 bugs.9front.org: update file structure sl
2016-12-19 22:48 ` [9front] " Kurt H Maier
@ 2016-12-20 1:23 ` kokamoto
2016-12-20 1:30 ` Stanley Lieber
1 sibling, 1 reply; 7+ messages in thread
From: kokamoto @ 2016-12-20 1:23 UTC (permalink / raw)
To: 9front
>Proposed:
sorry, I cannot totaly understand what you say.
'Save' ? what save, who save?
'bugname' ? who names it?
'bugs@9front,org' ? what is this?
Please work a bit more for me like ...
Kenji
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [9front] bugs.9front.org: update file structure
2016-12-20 1:23 ` kokamoto
@ 2016-12-20 1:30 ` Stanley Lieber
2016-12-20 2:14 ` kokamoto
0 siblings, 1 reply; 7+ messages in thread
From: Stanley Lieber @ 2016-12-20 1:30 UTC (permalink / raw)
To: 9front
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 documented in the FQA.
In my previous post I was talking about modifying the big tracker from its current functionality to the new functionality I proposed in the message.
sl
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [9front] bugs.9front.org: update file structure
2016-12-20 1:30 ` Stanley Lieber
@ 2016-12-20 2:14 ` kokamoto
2016-12-20 2:27 ` sl
0 siblings, 1 reply; 7+ messages in thread
From: kokamoto @ 2016-12-20 2:14 UTC (permalink / raw)
To: 9front
Thanks.
I feel if I can write bug report clearly, I can fix the bug myself
probably. I don't feel such a system neccessary, sorry.
In many cases, I don't know where I am when I meet a serious
bug to me. Even don't it's bug or my fail. ☺
However, that's my personal case, I don't disagree your proposal.
Kenji
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-12-20 2:27 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-19 22:23 bugs.9front.org: update file structure sl
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
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).