From: Michael Ellerman <michael@ellerman.id.au>
To: Jeff Brower <jbrower@signalogic.com>
Cc: linuxppc-dev@ozlabs.org, David Miller <davem@davemloft.net>
Subject: Re: What is with all these unsubscribe messages
Date: Tue, 06 Jan 2009 14:06:59 +1100 [thread overview]
Message-ID: <1231211219.8460.69.camel@localhost> (raw)
In-Reply-To: <32909.64.219.188.227.1231208926.squirrel@office.signalogic.com>
[-- Attachment #1: Type: text/plain, Size: 1732 bytes --]
On Mon, 2009-01-05 at 20:28 -0600, Jeff Brower wrote:
> David-
>
> > From: Ben Warren <biggerbadderben@gmail.com>
> > Date: Mon, 05 Jan 2009 17:27:06 -0800
> >
> >> I expect they're all people, like myself, that have been bumped here
> >> from the ppc_embedded list and aren't used to all the traffic.
> >
> > This is why, as a policy, we never allow propagation of subscribers
> > from old lists to new ones created at vger.kernel.org
> >
> > Everyone must go through the motions of adding themselves to the new
> > list.
> >
> > If you allow the propagation, it's essentially an act of putting
> > someone onto a mailing list without having their permission to do so.
> >
> > And the result is what we've seen here for the past few days. If
> > those people on the embedded list were truly interested in the
> > linuxppc-dev list content, they would have added themselves.
>
> I completely disagree. I'm glad the embedded PC list owners were thoughtful enough to migrate me to the new list.
> They are experts, they know what they're doing, and I trust their judgment.
>
> My only complaint is that the new subject lines don't have the widely used "[group-name]" prefix. I might guess that
> some people rely on that to organize e-mail searches for specific group content.
Instead they have "List-Id: Linux on PowerPC Developers Mail List
<linuxppc-dev.ozlabs.org>" in the headers, which any modern mailer
should be able to grok.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-06 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 1:03 What is with all these unsubscribe messages Matt Gessner
2009-01-06 1:07 ` Sean MacLennan
2009-01-06 1:27 ` Ben Warren
2009-01-06 1:59 ` David Miller
2009-01-06 2:28 ` Jeff Brower
2009-01-06 3:05 ` Ken MacLeod
2009-01-06 3:06 ` Michael Ellerman [this message]
2009-01-06 4:09 ` David Miller
2009-01-06 2:53 ` Stephen Rothwell
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=1231211219.8460.69.camel@localhost \
--to=michael@ellerman.id.au \
--cc=davem@davemloft.net \
--cc=jbrower@signalogic.com \
--cc=linuxppc-dev@ozlabs.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).