From: Carlos Maiolino <cmaiolino@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Troy McCorkell <tdm@sgi.com>, carlos.e.r@opensuse.org, xfs@oss.sgi.com
Subject: Re: What's up with this list?
Date: Mon, 21 Sep 2015 09:03:12 +0200 [thread overview]
Message-ID: <20150921070312.GA2617@redhat.com> (raw)
In-Reply-To: <20150918225624.GF26895@dastard>
On Sat, Sep 19, 2015 at 08:56:24AM +1000, Dave Chinner wrote:
> On Fri, Sep 18, 2015 at 11:01:45AM -0500, Troy McCorkell wrote:
> > xfs@oss.sgi.com is an open list and does not require people to be members
> > of the list to post to it. The spam filters applied to
> > xfs@oss.sgi.com are
> > as aggressive as they can be and still allow for an open list.
> >
> > Next option would be to add a moderator to the list. Adding a moderator
> > would interfere with non-list members posting to the list.
>
> Moderation is not an option because of this interference and the
> burden it puts on the moderator to respond in a timely fashion.
>
> If the spam rejection does not improve our next option is to move to
> the linux-xfs@vger.kernel.org list - the vger infrastructure is not
> perfect, but it does have better spam rejection than the current
> filtering on this list. This may be the best long-term solution to
> the problem, but it does involve short term pain for everyone.
>
+1 for that, the pain is not that much, and we've discussed moving xfs list to
vger.kernel.org for a while, I really don't see a reason to do so, other than
people needing to update their e-mail addresses and maybe git configurations. To
relief even more the pain, xfs@sgi, could just forward the e-mails to linux-xfs
with a InReplyTo modified to linux-xfs even.
Althouh, I'm not sure how feasible is the last part.
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
--
Carlos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-21 7:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 12:46 What's up with this list? Carlos E. R.
2014-09-18 15:33 ` Troy McCorkell
2015-09-16 12:53 ` Carlos E. R.
2015-09-17 16:54 ` Troy McCorkell
2015-09-17 18:31 ` Carlos E. R.
2015-09-18 16:01 ` Troy McCorkell
2015-09-18 22:56 ` Dave Chinner
2015-09-19 0:30 ` Carlos E. R.
2015-09-19 11:52 ` Carlos E. R.
2015-09-21 10:02 ` Carlos E. R.
2015-09-19 5:12 ` Fanael Linithien
2015-09-19 11:46 ` Arkadiusz Miśkiewicz
2015-09-21 7:03 ` Carlos Maiolino [this message]
2015-09-21 15:13 ` Troy McCorkell
2015-09-21 17:36 ` Carlos E. R.
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=20150921070312.GA2617@redhat.com \
--to=cmaiolino@redhat.com \
--cc=carlos.e.r@opensuse.org \
--cc=david@fromorbit.com \
--cc=tdm@sgi.com \
--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