From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: bug tracker down
Date: Wed, 4 Jan 2017 21:58:26 -0500 [thread overview]
Message-ID: <C39BD760-E95D-4945-86B1-E6980A04FD70@stanleylieber.com> (raw)
Recent updates to 9front have broken multiple pieces of what constituted the bug tracker. Presently, sending mail to 9front-bugs-open@9front.org will result in an error. Previously submitted bugs are still available via 9P and at the bugs.9front.org website, and the 9front-bugs mailing list remains functional. But creating new bugs is currently impossible.
I will send another message to this mailing list once services are fully restored.
sl
reply other threads:[~2017-01-05 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=C39BD760-E95D-4945-86B1-E6980A04FD70@stanleylieber.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).