Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Bug tracking system
Date: Thu, 14 Aug 2014 17:22:27 +0200	[thread overview]
Message-ID: <20140814152227.GB17617@linux-mips.org> (raw)
In-Reply-To: <53ECD126.7090103@imgtec.com>

On Thu, Aug 14, 2014 at 04:09:26PM +0100, James Hogan wrote:

> On 14/08/14 15:55, Ralf Baechle wrote:
> > While I'm tinkering with the system - linux-mips.org still has no
> > bug tracking system to track bugs and so issues get forgotten also the
> > only system we have to track feature requests and other to-do items
> > currently is the to do page in the wiki.  But the wiki isn't the best
> > medium for this purpose.  So should we install something like bugzilla -
> > which I personally never liked - or other tracking system?  Suggestions?
> 
> If bugzilla is to be used, would it make sense to use the kernel.org
> bugzilla which already has a MIPS category, rather than setting up a new
> one?
> 
> https://bugzilla.kernel.org/buglist.cgi?product=Platform%20Specific%2FHardware&component=MIPS&resolution=---

Indeed why not.  Might even talk to the kernel.org admins to have it show
up as bugzilla.linux-mips.org or something like that.

I personally like the Debian bug tracking system but I'm not sure how
well it integrates with esotheric MTAs such as zmailer and how bad spam
issues would be.

  Ralf

      parent reply	other threads:[~2014-08-14 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-14 14:55 Bug tracking system Ralf Baechle
2014-08-14 15:09 ` James Hogan
2014-08-14 15:09   ` James Hogan
2014-08-14 15:22   ` Ralf Baechle [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=20140814152227.GB17617@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-mips@linux-mips.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