From: Russell Cattelan <cattelan@thebarn.com>
To: xfs@oss.sgi.com
Subject: Re: repeated abuses of the XFS list
Date: Thu, 05 Apr 2012 21:01:55 -0500 [thread overview]
Message-ID: <4F7E4E93.6050803@digitalelves.com> (raw)
In-Reply-To: <4F7E3C57.3030103@thebarn.com>
Sorry for what appears to be an off topic posts.
These emails were part of a non-xfs related conversation
that was forwarded to list by Peter Grandi.
While I did write these emails I did not sent them to the list.
If any additional emails on this topic show up they will not have come
directly from me.
-Russell
On 4/5/12 7:44 PM, Russell Cattelan wrote:
> Well I'm afraid I'm going to respectfully disagree.
> I don't have the full story of everything that happened
> but none of the post you pointed out are totally off topic.
> There seems to be some question about what you have said previously
> about XFS, which to me would seem on topic.
>
> I have forwarded your email to Christoph and the other prominent members
> of the XFS team and if they feel further action is warranted we
> can revisit the issue. Based on what you have sent I do
> not feel there is grounds for action.
>
> -Russell
>
>
> On 4/5/12 7:20 PM, Peter Grandi wrote:
>>> You must be joking! I'm not about to ban one of the most
>>> knowledgeable and productive xfs developers from the email
>>> list.
>>
>> Well, if one of these guys post offtopic and malicious rants, I
>> guess that his being an XFS developer should not matter.
>>
>> With being an XFS developer comes also some responsibility to
>> maintain a technical and professional tone in the XFS mailing
>> list, and not to abuse his position. Same for the others.
>>
>>> I see nothing particularly offensive about these posts.
>>
>> They personal attacks about competence and character. They are
>> pure flames, and because they are coordinated they seem to be
>> mobbing.
>>
>> To me, you seem to be expliciting endorsing the use of the XFS
>> mailing list to publish "ad hominem" attacks and mobbing.
>>
>>> I can understand you may upset about what Christoph said but
>>> he has every right to state his opinions on things no matter
>>> how much you disagree.
>>
>> But his opinions are on offtopic "things": the topic of the XFS
>> mailing list is XFS, not people's competence or character, or
>> rants/attacks on people.
>>
>> Some of the links I have sent you contain no technical content,
>> purely personal attacks. How can this be legitimate XFS content?
>>
>> I think that it is your responsbility to ensure that posts are
>> kept ontopic, and you assume responsibility for their content
>> otherwise.
>
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-04-06 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20350.11825.59139.309447@tree.ty.sabi.co.UK>
2012-04-05 23:55 ` repeated abuses of the XFS list Russell Cattelan
[not found] ` <20350.14023.770391.715110@tree.ty.sabi.co.UK>
2012-04-06 0:44 ` Russell Cattelan
2012-04-06 2:01 ` Russell Cattelan [this message]
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=4F7E4E93.6050803@digitalelves.com \
--to=cattelan@thebarn.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