From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 21:27:37 -0500 [thread overview]
Message-ID: <be7bb6d8e341950cfd9ce6bebe3e7cf1@pav1.example.com> (raw)
In-Reply-To: <5d5374c6e3ba3de61ce42cecd2225b70@ci5dell.jitaku.localdomain>
> I feel if I can write bug report clearly, I can fix the bug myself
> probably. I don't feel such a system neccessary, sorry.
That's fine. The bug tracker was created because cinap and aiju asked
for it. In the end, it is not used much.
sl
prev parent reply other threads:[~2016-12-20 2:27 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
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 [this message]
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=be7bb6d8e341950cfd9ce6bebe3e7cf1@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).