From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] 9bugs: how to add a comment?
Date: Sat, 18 Aug 2018 14:06:59 +0100 [thread overview]
Message-ID: <1534597619.2668484.1478303560.3A088ED2@webmail.messagingengine.com> (raw)
In-Reply-To: <725D9D96A66959EF2B21ADE86931EBF1@ewsd.inri.net>
On Sat, Aug 18, 2018, at 4:25 AM, sl@stanleylieber.com wrote:
>
> The bug tracker sucks. It was left half-finished and has never really
> been used by the developers (I close all the bugs).
Ohhh right! Well, if the developers don't really use it, I can relax. :)
>
> 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.
That looks like a big project. I don't think I'd like the various interfaces too much, but then, much like email clients, all bug trackers suck. At least with this one's filesystem interface, complex search queries will be relatively easy. It's got me wondering what I'll do for bug tracking in my Forth OS; getting my ideas going. :) Of course, that's a big project too...
--
The lyf so short, the craft so long to lerne. -- Chaucer
next parent reply other threads:[~2018-08-18 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <725D9D96A66959EF2B21ADE86931EBF1@ewsd.inri.net>
2018-08-18 13:06 ` Ethan Gardener [this message]
2020-04-12 1:17 ` sl
[not found] <E865626C3D0E672853C735EBD59B3CD6@ewsd.inri.net>
2020-04-12 3:21 ` ori
[not found] <9E2C5A2621CF0E9D0257447D45065F28@ewsd.inri.net>
2018-08-18 9:44 ` hiro
2018-08-18 3:25 sl
-- 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=1534597619.2668484.1478303560.3A088ED2@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--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).