From: "Lista Unx" <lista.unx@gmail.com>
To: Dave Chinner <david@fromorbit.com>,
"Carlos E. R." <robin.listas@telefonica.net>
Cc: XFS mail list <xfs@oss.sgi.com>
Subject: Re: Spam on this list
Date: Thu, 4 Aug 2016 14:34:11 +0300 [thread overview]
Message-ID: <3D58B7EB9A964054997E0E370C98251D@dinulap> (raw)
In-Reply-To: 20160803231529.GX16044@dastard
----- Original Message -----
From: "Dave Chinner" <david@fromorbit.com>
To: "Carlos E. R." <robin.listas@telefonica.net>
Cc: "XFS mail list" <xfs@oss.sgi.com>
Sent: Thursday, August 04, 2016 2:15 AM
Subject: Re: Spam on this list
> Yes, that is the fundamental issue - spam filtering is essentially
> controlled by SGI's internal infrastructure, which we have little
> option on.
>
> What it comes down to is whether we continue to use this list
> (xfs@oss.sgi.com) or whether we move to linux-xfs@vger.kernel.org
> so we get much more robust and up-to-date spam filtering. The issue
> with doing this is forcing everyone to resubscribe, and then
> capturing everything that is still sent to xfs@oss.sgi.com.
>
> That said, I'm seriously tempted right now just to say "we're moving
> to vger" and asking everyone to resubscribe to that list, and then
> making xfs@oss.sgi.com respond with "list moved to vger, please
> repost there". i.e. not even put a forwarding gateway in place.
>
> If we do that, then I'll also shut down all the XFS git trees on
> oss.sgi.com - I'll add commits to the them to say "go to
> kernel.org". I'll need to work something out for the tarball
> releases, but kernel.org does have functionality for that, too, so
> that may just be a small change of process on my end (i.e. use kup).
> Once that is done, we'll be running completely on community provided
> infrastructure....
>
> Thoughts?
I completely agree, is a good idea to move to a new place where more filters
are already in place. It is a small change on user's side and benefits are
for everyone. I cannot see any cons to not do it. It probably will be the
best to keep also a message for newcommers and also for robots, that list
has been moved to vger and new way to subscribe.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-04 11:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 9:01 partition 100% full No space left on device. looks like xfs is corrupted or a bug Lista Unx
2016-07-29 10:48 ` Carlos E. R.
2016-07-29 14:27 ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 14:03 ` partition 100% full No space left on device. looks like xfs is corrupted " Brian Foster
2016-07-29 14:37 ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 15:20 ` Brian Foster
2016-07-29 21:49 ` partition 100% full No space left on device. looks like xfs is corrupted " Eric Sandeen
2016-08-01 11:24 ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-07-29 23:35 ` partition 100% full No space left on device. looks like xfs is corrupted " Dave Chinner
2016-08-01 12:00 ` partition 100% full No space left on device. looks like xfs iscorrupted " Lista Unx
2016-08-01 12:23 ` Carlos E. R.
2016-08-02 17:34 ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 17:34 ` Lista Unx
2016-08-01 16:51 ` partition 100% full No space left on device. looks like xfs iscorrupted " Chris Murphy
2016-08-02 17:58 ` partition 100% full No space left on device. looks like xfsiscorrupted " Lista Unx
2016-08-02 19:11 ` Troy McCorkell
2016-08-03 12:59 ` Spam on this list [Was: Re: partition 100% full No space left on device. looks like xfs iscorrupted or a bug] Carlos E. R.
2016-08-03 13:21 ` Martin Steigerwald
2016-08-03 13:34 ` Carlos E. R.
2016-08-03 23:15 ` Spam on this list Dave Chinner
2016-08-03 23:29 ` Darrick J. Wong
2016-08-04 0:51 ` Carlos E. R.
2016-08-04 11:34 ` Lista Unx [this message]
2016-08-04 13:40 ` Troy McCorkell
2016-08-04 15:49 ` Martin Steigerwald
2016-08-05 8:25 ` Carlos Eduardo Maiolino
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=3D58B7EB9A964054997E0E370C98251D@dinulap \
--to=lista.unx@gmail.com \
--cc=david@fromorbit.com \
--cc=robin.listas@telefonica.net \
--cc=xfs@oss.sgi.com \
/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).