From: Hugh Blemings <hugh@blemings.org>
To: Satyam Sharma <satyam@infradead.org>
Cc: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [Cbe-oss-dev] [PATCH] PS3: Update MAINTAINERS
Date: Fri, 24 Aug 2007 16:48:48 +1000 [thread overview]
Message-ID: <20070824164848.b771f037.hugh@blemings.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0708241210560.20322@enigma.security.iitk.ac.in>
Hiya Satyam, All,
> > > [PATCH] PS3: Update MAINTAINERS
> > >
> > > Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org> is an
> > > subscribers-only mailing list.
> > >
> > > Signed-off-by: Satyam Sharma <satyam@infradead.org>
> > >
> > > [...]
> >
> > As per recent discussions...
> >
> > The list is moderated for SPAM prevention, messages from valid senders
> > will be forwarded manually and their email added to the whitelist.
> >
> > I've changed the list config so that it no longer generates the
> > "subscriber-only" notification.
>
> So ... if someone (!subscriber && !whitelisted) sends a message, it stays
> put somewhere till you get to it and determine whether it is relevant or
> not, and either (1) forward it on to the list if appropriate, or (2) drop
> it if detected as spam. And no "notifications" are ever sent out to
> genuine / well-meaning posters during this process. Right?
Correct.
I aim to check messages at least once a day, typically more like three or four times.
There is a (increasingly brief it seems) period where I sleep so things may languish during that period, or if I've gone bush or some such :)
Jokes aside, am in the process of getting someone in Europe to co-moderate so we've some redundancy.
> > On this basis I recommended the patch be NAKd so that people aren't put
> > off copying the list where appropriate.
>
> Fair enough, if my understanding (as mentioned above) is correct, then I
> believe the patch achieved a greater purpose than what it was originally
> sent out for!
No prob, good result all round it seems.
Cheers,
Hugh
next prev parent reply other threads:[~2007-08-24 6:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 11:20 [PATCH 000 of 6] A few block-layer tidy-up patches NeilBrown
2007-08-16 11:20 ` [PATCH 001 of 6] Merge blk_recount_segments into blk_recalc_rq_segments NeilBrown
2007-08-16 11:21 ` [PATCH 002 of 6] Introduce rq_for_each_segment replacing rq_for_each_bio NeilBrown
2007-08-17 7:13 ` Geert Uytterhoeven
2007-08-18 14:37 ` Satyam Sharma
2007-08-18 14:30 ` Jan Engelhardt
2007-08-18 14:48 ` Satyam Sharma
2007-08-20 11:21 ` Geert Uytterhoeven
2007-08-20 12:46 ` Jan Engelhardt
2007-08-21 1:38 ` Satyam Sharma
2007-08-21 7:09 ` Geert Uytterhoeven
2007-08-21 9:46 ` Satyam Sharma
2007-08-21 9:52 ` Geert Uytterhoeven
2007-08-21 10:41 ` [PATCH] PS3: Update MAINTAINERS Satyam Sharma
2007-08-21 19:01 ` Geoff Levand
2007-08-21 20:01 ` Joe Perches
2007-08-21 20:06 ` Rene Herman
2007-08-21 20:17 ` Geoff Levand
2007-08-21 20:33 ` Rene Herman
2007-08-21 20:48 ` Satyam Sharma
2007-08-21 20:41 ` Rene Herman
2007-08-21 20:47 ` Joe Perches
2007-08-21 21:58 ` Hugh Blemings
2007-08-23 18:14 ` Matt Mackall
2007-08-24 5:52 ` Hugh Blemings
2007-08-21 20:10 ` Geoff Levand
2007-08-24 6:25 ` [Cbe-oss-dev] " Hugh Blemings
2007-08-24 6:47 ` Satyam Sharma
2007-08-24 6:48 ` Hugh Blemings [this message]
2007-08-16 11:21 ` [PATCH 003 of 6] Fix various abuse of bio fields in umem.c NeilBrown
2007-08-16 11:21 ` [PATCH 004 of 6] New function blk_req_append_bio NeilBrown
2007-08-16 11:21 ` [PATCH 005 of 6] Stop exporting blk_rq_bio_prep NeilBrown
2007-08-16 11:21 ` [PATCH 006 of 6] Share code between init_request_from_bio and blk_rq_bio_prep NeilBrown
2007-08-16 11:36 ` [PATCH 000 of 6] A few block-layer tidy-up patches Jens Axboe
2007-08-17 0:40 ` Neil Brown
2007-08-17 6:17 ` Jens Axboe
2007-08-17 7:21 ` Neil Brown
2007-08-17 12:37 ` Jens Axboe
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=20070824164848.b771f037.hugh@blemings.org \
--to=hugh@blemings.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=satyam@infradead.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
all inboxes | Powered by JetHome®