From: <Tim.Bird@sony.com>
To: <viro@ZenIV.linux.org.uk>, <visionsofalice@redchan.it>
Cc: linux-kernel-owner@vger.kernel.org, rms@gnu.org,
ksummit-discuss@lists.linuxfoundation.org, mishi@linux.com,
gregkh@linuxfoundation.org, bruce@perens.com,
linux-kernel@vger.kernel.org, esr@thyrsus.com,
moglen@columbia.edu, bkuhn@sfconservancy.org, neil@brown.name,
editor@lwn.net
Subject: Re: [Ksummit-discuss] The linux devs can rescind their license grant.
Date: Sat, 27 Oct 2018 16:18:12 +0000 [thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF88A2A727@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20181027073241.GM32577@ZenIV.linux.org.uk>
> -----Original Message-----
> From: Al Viro
>
> On Sat, Oct 27, 2018 at 06:52:44AM +0000, visionsofalice@redchan.it wrote:
> > Al: the FSF was so insistent on the adoption of the GPL version 3
> > because the GPL version 2 is not operative against the grantor.
>
> Anonymous wankstain: sod off and learn to troll properly. It *is* an art
> form, and the one you are clearly not up to.
>
> D-. For the effort and successful use of spellchecker. The style and
> contents are about F to E-, unfortunately, so take that in the spirit
> in which it is offered. As a participation award, that is.
Al,
Can you please, even in the face of comments you find irritating, keep your responses
more civil? Calling someone a "wankstain" is unprofessional, and we're trying
to raise the level of discourse here.
>
> *plonk*
I think this part of the response was sufficient to communicate that you do not
take the suggestions of the other party seriously. And it communicates
to others the right approach. If someone thinks that another person is acting in bad
faith, I think it's better to just stop listening to that person, and let that person know
it, and to let other community members know it. De-escalation is preferable to
engagement when working with someone who is acting in bad faith.
Although I disagree with the approach used in the top portion of this message, I am
grateful that you are committed to protecting Linux and our development community.
Regards,
-- Tim
next prev parent reply other threads:[~2018-10-27 16:18 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 13:49 [Ksummit-discuss] [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document Greg Kroah-Hartman
2018-10-20 13:49 ` [Ksummit-discuss] [PATCH 1/7] Code of conduct: Fix wording around maintainers enforcing the code of conduct Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 2/7] Code of Conduct Interpretation: Add document explaining how the Code of Conduct is to be interpreted Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 3/7] Code of Conduct Interpretation: Properly reference the TAB correctly Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 4/7] Code of Conduct: Provide links between the two documents Greg Kroah-Hartman
2018-10-20 13:50 ` [Ksummit-discuss] [PATCH 5/7] Code of Conduct Interpretation: Put in the proper URL for the committee Greg Kroah-Hartman
2018-10-20 19:01 ` Geert Uytterhoeven
2018-10-21 7:18 ` Greg KH
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 6/7] Code of Conduct: Change the contact email address Greg Kroah-Hartman
2018-10-20 18:28 ` Alan Cox
2018-10-20 18:45 ` Trond Myklebust
2018-10-20 19:14 ` jonsmirl
2018-10-21 8:27 ` Theodore Y. Ts'o
2018-10-21 9:23 ` Greg KH
2018-10-20 19:24 ` Tim.Bird
2018-10-20 20:07 ` Trond Myklebust
2018-10-21 0:13 ` Alan Cox
2018-10-21 6:19 ` Thomas Gleixner
2018-10-20 20:13 ` James Bottomley
2018-10-20 13:51 ` [Ksummit-discuss] [PATCH 7/7] MAINTAINERS: Add an entry for the code of conduct Greg Kroah-Hartman
2018-10-21 21:20 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-21 22:26 ` Josh Triplett
2018-10-21 23:37 ` Theodore Y. Ts'o
2018-10-23 1:44 ` NeilBrown
2018-10-22 20:26 ` NeilBrown
2018-10-22 22:46 ` Theodore Y. Ts'o
2018-10-23 1:31 ` NeilBrown
2018-10-23 6:26 ` Dan Carpenter
2018-10-23 6:40 ` Al Viro
2018-10-23 6:46 ` Dan Carpenter
2018-10-23 3:31 ` Al Viro
2018-10-23 4:25 ` NeilBrown
2018-10-23 4:52 ` Al Viro
2018-10-23 5:28 ` NeilBrown
2018-10-23 6:00 ` Al Viro
2018-10-23 20:45 ` NeilBrown
2018-10-23 8:11 ` Theodore Y. Ts'o
2018-10-23 14:22 ` Rainer Fiebig
2018-10-23 15:43 ` Theodore Y. Ts'o
2018-10-23 21:14 ` NeilBrown
2018-10-24 12:16 ` Josh Triplett
2018-10-25 21:14 ` NeilBrown
2018-10-27 1:10 ` Josh Triplett
2018-10-28 21:48 ` NeilBrown
2018-11-01 16:45 ` Paul E. McKenney
2018-11-01 21:11 ` Josh Triplett
2018-11-02 13:13 ` Paul E. McKenney
2018-11-01 21:50 ` NeilBrown
2018-11-02 13:33 ` Paul E. McKenney
2018-11-03 8:36 ` NeilBrown
2018-11-03 17:37 ` Paul E. McKenney
2018-11-03 21:06 ` NeilBrown
2018-11-03 22:23 ` Paul E. McKenney
2018-11-02 13:52 ` James Bottomley
2018-11-04 10:35 ` Geert Uytterhoeven
2018-10-21 22:33 ` Joe Perches
2018-10-21 22:37 ` Randy Dunlap
2018-10-22 9:09 ` Rainer Fiebig
2018-10-22 11:02 ` James Bottomley
2018-10-24 8:49 ` Laura Abbott
[not found] ` <185b786a2bd6e8d527dca161dc42e4f1@redchan.it>
2018-10-25 8:19 ` [Ksummit-discuss] The linux devs can rescind their license grant Greg Kroah-Hartman
[not found] ` <20181025193901.GD26403@thyrsus.com>
2018-10-25 20:47 ` Theodore Y. Ts'o
[not found] ` <20181025214123.GA2448@thyrsus.com>
2018-10-25 22:12 ` NeilBrown
[not found] ` <20181025223813.GA5137@thyrsus.com>
2018-10-25 22:52 ` NeilBrown
2018-11-04 10:47 ` Geert Uytterhoeven
2018-10-25 23:06 ` Al Viro
[not found] ` <20181026022836.GA12924@thyrsus.com>
2018-10-26 5:49 ` Al Viro
[not found] ` <75eb4a46c8a2c1d4a927760fd1f2009d@redchan.it>
2018-10-27 7:32 ` Al Viro
2018-10-27 16:18 ` Tim.Bird [this message]
2018-10-27 22:09 ` Jiri Kosina
[not found] ` <CAK2MWOtNUTjWy5pTcGco5DNurqNCc=9CfDJ-Ko-K+6HDC55ikg@mail.gmail.com>
2018-10-27 23:40 ` Al Viro
2018-10-28 21:13 ` NeilBrown
2018-10-29 22:31 ` Bradley M. Kuhn
2018-10-25 22:02 ` [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document NeilBrown
2018-10-25 8:06 ` Pavel Machek
[not found] ` <2341648.lzjnUGKk1z@siriux>
2018-10-25 22:18 ` NeilBrown
[not found] ` <ffeb597c-9ca2-cf21-ba52-2146ab20c83a@mailbox.org>
2018-10-26 22:40 ` NeilBrown
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=ECADFF3FD767C149AD96A924E7EA6EAF88A2A727@USCULXMSG01.am.sony.com \
--to=tim.bird@sony.com \
--cc=bkuhn@sfconservancy.org \
--cc=bruce@perens.com \
--cc=editor@lwn.net \
--cc=esr@thyrsus.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mishi@linux.com \
--cc=moglen@columbia.edu \
--cc=neil@brown.name \
--cc=rms@gnu.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=visionsofalice@redchan.it \
/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