From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 17:55:07 -0500 [thread overview]
Message-ID: <724b328bffd6049f24eb0be0c359e556@pav1.example.com> (raw)
In-Reply-To: <20161219224856.GB40372@wopr>
> 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
next prev parent reply other threads:[~2016-12-19 22:55 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 ` [9front] " Kurt H Maier
2016-12-19 22:55 ` sl [this message]
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=724b328bffd6049f24eb0be0c359e556@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).