From: Peter Samuelson <peter@cadcamlab.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: YMF PCI - thanks, glitches, patches (fwd)
Date: Thu, 7 Dec 2000 20:37:57 -0600 [thread overview]
Message-ID: <20001207203756.P6567@cadcamlab.org> (raw)
In-Reply-To: <E1441FJ-0002QX-00@the-village.bc.nu> <Pine.LNX.4.30.0012071108220.23591-100000@fonzie.nine.com>
In-Reply-To: <Pine.LNX.4.30.0012071108220.23591-100000@fonzie.nine.com>; from proski@gnu.org on Thu, Dec 07, 2000 at 11:44:55AM -0500
[AC]
> > sound-list@redhat.com is alive and well however.
[Pavel Roskin]
> You cannot imagine how frustrating it was to search for the archive.
> I couldn't find an up-to-date archive, and www.kernel.org keeps
> silence about mailing lists. I cannot afford subscribing to every
> list just to slightly polish support for my hardware.
Linus does take patches to the MAINTAINERS file from time to time. (:
In my opinion, the L: entries of MAINTAINERS ought to have URLs for
list archives, where available:
L: sound-list@redhat.com, <URL:http://www.xxxxxxx>
Perhaps archive URLs should be on W: lines but I think the L: lines are
appropriate -- keep related information together.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-08 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 18:12 YMF PCI - thanks, glitches, patches (fwd) Pavel Roskin
2000-12-06 19:02 ` Pete Zaitcev
2000-12-06 20:00 ` Pavel Roskin
2000-12-06 20:59 ` Pavel Roskin
2000-12-06 23:12 ` Pete Zaitcev
2000-12-07 13:37 ` Alan Cox
2000-12-07 16:44 ` Pavel Roskin
2000-12-07 16:48 ` Alan Cox
2000-12-08 2:37 ` Peter Samuelson [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=20001207203756.P6567@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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