9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] bugs.9front.org: update file structure
Date: Mon, 19 Dec 2016 20:30:11 -0500	[thread overview]
Message-ID: <68D78BEB-BD48-45E2-B859-11AFC53C59DB@stanleylieber.com> (raw)
In-Reply-To: <91ad4a647b02fe6c35f32c258a44c5ba@ci5dell.jitaku.localdomain>

Kenji,

There exists a very rudimentary 9front bug tracker at:

        http://bugs.9front.org

You can submit bugs via e-mail and subscribe to the 9front-bugs mailing list, where all these submissions are ultimately forwarded. This is all documented in the FQA.

In my previous post I was talking about modifying the big tracker from its current functionality to the new functionality I proposed in the message.

sl




  reply	other threads:[~2016-12-20  1:30 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 [this message]
2016-12-20  2:14     ` kokamoto
2016-12-20  2:27       ` sl

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=68D78BEB-BD48-45E2-B859-11AFC53C59DB@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).