From: James Hogan <james.hogan@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>, <linux-mips@linux-mips.org>
Subject: Re: Bug tracking system
Date: Thu, 14 Aug 2014 16:09:26 +0100 [thread overview]
Message-ID: <53ECD126.7090103@imgtec.com> (raw)
In-Reply-To: <20140814145558.GA17477@linux-mips.org>
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=---
Cheers
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Bug tracking system
Date: Thu, 14 Aug 2014 16:09:26 +0100 [thread overview]
Message-ID: <53ECD126.7090103@imgtec.com> (raw)
Message-ID: <20140814150926.rJMXcXN_YbSaiUwQLQHUyBqaAb21mSjmlqwmEnIhos8@z> (raw)
In-Reply-To: <20140814145558.GA17477@linux-mips.org>
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=---
Cheers
James
next prev parent reply other threads:[~2014-08-14 15:09 UTC|newest]
Thread overview: 10+ 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 [this message]
2014-08-14 15:09 ` James Hogan
2014-08-14 15:22 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-04-13 20:49 Ian Pratt
2005-04-13 21:06 ` Nivedita Singhvi
2005-04-13 21:08 ` Anthony Liguori
2005-04-13 21:17 ` Paul Larson
2005-04-13 23:02 ` Ryan Harper
2005-04-13 17:35 Paul Larson
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=53ECD126.7090103@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.