From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.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 10:54:43 +0100 [thread overview]
Message-ID: <20080217095443.GA9842@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802171050220.6848@anakin>
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.
Sam
next prev parent reply other threads:[~2008-02-17 9:54 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 [this message]
2008-02-17 10:36 ` Geert Uytterhoeven
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=20080217095443.GA9842@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.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 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).