From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: list of outstanding issues somewhere?
Date: Mon, 19 Jul 2004 13:44:57 +0200 [thread overview]
Message-ID: <20040719114502.1D15AC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 19 Jul 2004 06:59:53 EDT." <Pine.LNX.4.60.0407190654480.3673@dell.enoriver.com>
In message <Pine.LNX.4.60.0407190654480.3673@dell.enoriver.com> you wrote:
>
> it would be great if there was a list of outstanding issues one
> could check to see that a problem they're having is already on
> someone's radar screen -- not necessarily even being actively worked
> on, just acknowledged that that issue exists. a TO DO list? just
> curious.
Maybe we could even have a (searchable) patch database so that
submissions, even if rejected, don't get lost completely.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
The Buddha, the Godhead, resides quite as comfortably in the circuits
of a digital computer or the gears of a cycle transmission as he does
at the top of a mountain or in the petals of a flower.
- R. Pirsig, "Zen and the Art of Motorcycle Maintenance"
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-19 11:44 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 [this message]
2004-07-19 12:11 ` Gary Thomas
2004-07-19 12:27 ` Robert P. J. Day
2004-07-19 12:41 ` Gary Thomas
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=20040719114502.1D15AC109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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).