From: "Michel Dänzer" <michel@daenzer.net>
To: Dave Airlie <airlied@linux.ie>
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: drm mailing list?
Date: Tue, 03 Aug 2004 13:08:53 +0200 [thread overview]
Message-ID: <1091531333.4617.45.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0408031148580.31513@skynet>
On Tue, 2004-08-03 at 11:53 +0100, Dave Airlie wrote:
> Okay the people who are interested in the future of the DRM seem to be
> fairly evenly split between dri-devel and linux-kernel mailing lists,
>
> I'm not going to subscribe to lk (I've been there and I quite enjoy having
> a life :-), and I know a fair few lk people won't want to join dri-devel
> as DRM isn't the only thing going on there...
dri-devel is really low traffic compared to lkml though. I'd say the
kernel folks who are really interested should give it a try (a fair
number seems to be subscribed already) and shout if a dedicated list is
needed.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
prev parent reply other threads:[~2004-08-03 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 10:53 drm mailing list? Dave Airlie
2004-08-03 11:08 ` Michel Dänzer [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=1091531333.4617.45.camel@localhost \
--to=michel@daenzer.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.