From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9front@9front.org
Subject: Re: [9front] PROPOSAL: New 9front Bug Tracker
Date: Wed, 7 Feb 2018 18:08:44 -0800 (PST) [thread overview]
Message-ID: <alpine.BSF.2.21.1802071806310.19541@orthanc.ca> (raw)
In-Reply-To: <0181CC86F20462F489E422A79155DEE5@5ess.inri.net>
> The existing bug tracker sucks.
It would be helpful to know the, say, three most hated things about the
current regime :-) Knowing what you're running from can help guide where
you should be running to.
next prev parent reply other threads:[~2018-02-08 2:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 1:34 sl
2018-02-08 2:08 ` Lyndon Nerenberg [this message]
2018-02-08 8:37 ` [9front] " Julius Schmidt
2018-02-08 9:07 ` Kurt H Maier
2018-02-08 16:54 ` Ethan Grammatikidis
2018-02-08 23:23 ` Steve Simon
2018-02-08 23:56 ` Kurt H Maier
2018-02-08 2:55 sl
2018-02-09 3:01 sl
2018-02-09 3:15 sl
2018-02-09 3:21 sl
2018-02-09 3:31 sl
2018-02-09 5:11 ` Eli Cohen
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=alpine.BSF.2.21.1802071806310.19541@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).