From: Carlos Eduardo Maiolino <cmaiolin@redhat.com>
To: Martin Steigerwald <martin@lichtvoll.de>
Cc: "Carlos E. R." <robin.listas@telefonica.net>, xfs@oss.sgi.com
Subject: Re: Spam on this list
Date: Fri, 5 Aug 2016 04:25:21 -0400 (EDT) [thread overview]
Message-ID: <784564312.1292141.1470385521968.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1693896.yYUZdOzIYq@merkaba>
>>
>> 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?
>Nice, so this time discussing spam on the list on the list may have a nice
>effect in the end.
>
>I completely agree and have no issues with resubscribung there.
>
>Thank you,
>--
>Martin
+1 here.
Honestly, I don't believe that moving to vger will be a big trouble for anyone other than the list maintainer who will need to set auto-respond messages.
And we have the advantage of moving it to a community provided infra as you said.
Let me know if you need any help with it, I'll be glad to help in this change
--
--Carlos
P.S. Martin, I apologize for the dup'ed e-mail, my MUA tricked me and I didn't copy xfs list on my previous reply..
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-05 8:25 UTC|newest]
Thread overview: 29+ 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
2016-08-04 13:40 ` Troy McCorkell
2016-08-04 15:49 ` Martin Steigerwald
2016-08-05 8:25 ` Carlos Eduardo Maiolino [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-23 14:41 spam " Pierre Frenkiel
[not found] <3E314A6E.2BFB8F88@plain.de>
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Philip Edelbrock
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=784564312.1292141.1470385521968.JavaMail.zimbra@redhat.com \
--to=cmaiolin@redhat.com \
--cc=martin@lichtvoll.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.