list of outstanding issues somewhere?
In message 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 at 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/
list of outstanding issues somewhere?
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. rday ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
list of outstanding issues somewhere?
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/
list of outstanding issues somewhere?
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 MLB Associates ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
list of outstanding issues somewhere?
On Mon, 2004-07-19 at 05:44, Wolfgang Denk wrote: > In message 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. BugZilla works great for this. -- Gary Thomas MLB Associates ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
