From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Tom Gall <tgall@rochcivictheatre.org>
Cc: "linuxppc-dev" <linuxppc-dev@lists.linuxppc.org>
Subject: bug list, who does things & so on.
Date: Mon, 22 Jan 2001 05:00:46 +0000 [thread overview]
Message-ID: <20010122050050.C7E792F0B0@apollo.valhalla.net> (raw)
>> And on that note... what do we have for bug-tracking systems for ppc kernel
>> related stuff? The collective memory of people on these to mailing lists?
>> I know someone mentioned a sourceforge page at one point.. is anyone useing
that?
>
> There is a sourceforge page. It hasn't been active which probably isn't a good
> thing. I know I'm keeping a bug list on paper that I know about. It's not a
long
> list. Happy to put it out on sourceforge... just don't want it all to be a
waste
> of time tho. I'm sure Olaf might have a bug or two to contribute 8-)
I was thinking about this the other day.
I would like to see a bug list for the sound stuff (not necessarily
separate) but so that:
(a) there is some record of what problems people have
(b) there is some way of putting app-related problems to the app maintainers
(see thread on endian-ness)
---
also it is not terribly obvious how it is decided if a patch is picked up
and by whom...
if patches are rejected (for some reason) - then it is useful for the patch
author to know this.
it sometimes has the appearance of being a sort of black hole for diffs...
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-01-22 5:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010122050050.C7E792F0B0@apollo.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tgall@rochcivictheatre.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).