From: Gary Thomas <gary@mlbassoc.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Wolfgang Denk <wd@denx.de>,
Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: list of outstanding issues somewhere?
Date: Mon, 19 Jul 2004 06:41:50 -0600 [thread overview]
Message-ID: <1090240909.2197.18.camel@hermes> (raw)
In-Reply-To: <Pine.LNX.4.60.0407190825510.9191@dell.enoriver.com>
On Mon, 2004-07-19 at 06:27, Robert P. J. Day wrote:
> On Mon, 19 Jul 2004, Gary Thomas wrote:
>
> >
> > On Mon, 2004-07-19 at 05:44, Wolfgang Denk wrote:
>
> >> Maybe we could even have a (searchable) patch database so that
> >> submissions, even if rejected, don't get lost completely.
> >
> > BugZilla works great for this.
>
> i'm not sure it needs to be that detailed or precise; i was just
> thinking of a more general summary of "things we're working on or that
> have to be dealt with at some point." whatever works.
The cool thing about BugZilla is that it can do that, as well as keep
track of patches (pending, etc), a history of what's happened with the
problem and much more. It's not hard to set up or administer and its
usefulness more than pays for the pain...
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-07-19 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 10:59 list of outstanding issues somewhere? Robert P. J. Day
2004-07-19 11:44 ` Wolfgang Denk
2004-07-19 12:11 ` Gary Thomas
2004-07-19 12:27 ` Robert P. J. Day
2004-07-19 12:41 ` Gary Thomas [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=1090240909.2197.18.camel@hermes \
--to=gary@mlbassoc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
--cc=wd@denx.de \
/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).