From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: linux-fbdev is moderated
Date: Sun, 17 Feb 2008 11:36:57 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0802171135300.6848@anakin> (raw)
In-Reply-To: <20080217095443.GA9842@uranus.ravnborg.org>
On Sun, 17 Feb 2008, Sam Ravnborg wrote:
> On Sun, Feb 17, 2008 at 10:50:52AM +0100, Geert Uytterhoeven wrote:
> > While linux-fbdev is subscribers-only, non-subscribers are not plainly
> > rejected, but moderated, so the casual patch/comment/question comes through.
>
> Have you considered moving this list to vger.kernel.org?
> Almost no spam so the moderation is not needed.
Sounds like a good idea to me...
Anyone who disagrees?
BTW, is there an easy way to tell people the address has changed? I.e.
unsubscribing everybody from the sf.net list and letting the sf.net
list send customized messages back to posters?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-17 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 9:50 [PATCH] MAINTAINERS: linux-fbdev is moderated Geert Uytterhoeven
2008-02-17 9:54 ` Sam Ravnborg
2008-02-17 10:36 ` Geert Uytterhoeven [this message]
2008-02-17 12:30 ` Paul Mundt
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=Pine.LNX.4.64.0802171135300.6848@anakin \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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).