From: Jes Sorensen <jes@sgi.com>
To: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
Cc: sammy@sammy.net, linux-m68k@vger.kernel.org,
James Simmons <jsimmons@infradead.org>,
linux-fbdev-devel@lists.sourceforge.net, zippel@linux-m68k.org,
Adrian Bunk <bunk@stusta.de>,
geert@linux-m68k.org, adaplas@pol.net
Subject: Re: [RFC: 2.6 patch] remove broken video drivers
Date: 23 Nov 2006 04:15:56 -0500 [thread overview]
Message-ID: <yq0fycav7zn.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <yq0k61mv8c2.fsf@jaguar.mkp.net>
Grrrrrrrrrr
Someone cross posted this to one of those idiotic messed up
members-only lists, namely linux-fbdev-devel.
I don't know who did that, but please leave that broken list off the
CC list when cross postings to properly configured mailing lists such
as linux-m68k and linux-kernel, until the admin of linux-fbdev-devel
gets a clue.
Jes
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-11-23 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 0:02 [RFC: 2.6 patch] remove broken video drivers Adrian Bunk
2006-11-18 10:34 ` Michael Schmitz
2006-11-18 19:55 ` Adrian Bunk
2006-11-19 11:46 ` Geert Uytterhoeven
2006-11-20 9:17 ` Michael Schmitz
2006-11-20 20:02 ` Adrian Bunk
2006-11-18 21:41 ` [RFC: 2.6 patch] remove broken video drivers (v2) Adrian Bunk
2006-11-23 9:08 ` [RFC: 2.6 patch] remove broken video drivers Jes Sorensen
2006-11-23 9:15 ` Jes Sorensen [this message]
2006-11-23 9:39 ` Geert Uytterhoeven
2006-11-23 9:49 ` Jes Sorensen
2006-11-20 16:51 ` James Simmons
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=yq0fycav7zn.fsf@jaguar.mkp.net \
--to=jes@sgi.com \
--cc=adaplas@pol.net \
--cc=bunk@stusta.de \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-m68k@vger.kernel.org \
--cc=sammy@sammy.net \
--cc=schmitz@mail.biophys.uni-duesseldorf.de \
--cc=zippel@linux-m68k.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).