From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] 9bugs: how to add a comment?
Date: Fri, 17 Aug 2018 23:25:05 -0400 [thread overview]
Message-ID: <20180818032505.x_oGZ3-Dd4vU6zx4Y0R239kyx4ERJIFOQE7HRkDnGRY@z> (raw)
In-Reply-To: 1534543208.1656276.1477898344.3CEB60CC@webmail.messagingengine.com
> i recently opened a bug by mailing 9front-bugs-open@9front.org , then
> realised i made a mistake. i replied to the received email from the
> list, (bugs.9front.org@9front.org), and got the reply from the list
> but i don't see it in /n/bugs/open/vncs_suicidal_tendencies . what's
> the correct procedure, please?
The bug tracker sucks. It was left half-finished and has never really
been used by the developers (I close all the bugs).
There is no way for a mere mortal to update the text of the
already-submitted bug.
My proposal for the replacement bug tracker was last updated
on 2018.02.12:
http://9front.org/bugtracker
Everybody stopped responding to the mailing list thread where
it was discussed, and I ran out of time.
sl
next reply other threads:[~2018-08-18 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 3:25 sl [this message]
[not found] <E865626C3D0E672853C735EBD59B3CD6@ewsd.inri.net>
2020-04-12 3:21 ` ori
[not found] <725D9D96A66959EF2B21ADE86931EBF1@ewsd.inri.net>
2018-08-18 13:06 ` Ethan Gardener
2020-04-12 1:17 ` sl
[not found] <9E2C5A2621CF0E9D0257447D45065F28@ewsd.inri.net>
2018-08-18 9:44 ` hiro
-- strict thread matches above, loose matches on Subject: below --
2018-08-17 22:04 cinap_lenrek
2018-08-17 22:09 ` Ethan Gardener
2018-08-17 22:11 ` Ethan Gardener
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=20180818032505.x_oGZ3-Dd4vU6zx4Y0R239kyx4ERJIFOQE7HRkDnGRY@z \
--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).