From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: list of outstanding issues somewhere?
Date: Mon, 19 Jul 2004 06:59:53 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0407190654480.3673@dell.enoriver.com> (raw)
is there, somewhere, a list of known issues/bugs/upcoming fixes for
the PPC-oriented kernel source? on a number of occasions, i've had
the bad timing to ask about something that was, in fact, in the
process of being patched or that someone was just about to start
working on, or that at least someone already knew about.
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.
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-07-19 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 10:59 Robert P. J. Day [this message]
2004-07-19 11:44 ` list of outstanding issues somewhere? 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
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=Pine.LNX.4.60.0407190654480.3673@dell.enoriver.com \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.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).