From: unconditionedwitness@redchan.it
To: dng@lists.dyne.org, linux-kernel@vger.kernel.org,
debian-user@lists.debian.org
Cc: rms@gnu.org, esr@thyrsus.com, moglen@columbia.edu,
bruce@perens.com, debian-ctte@lists.debian.org, editor@lwn.net,
torvalds@osdl.org, blukashev@sempervictus.com,
bkuhn@sfconservancy.org
Subject: ""The remedies you suggest, if they could even be legally done""
Date: Thu, 20 Sep 2018 04:01:01 +0000 [thread overview]
Message-ID: <22625a1ca4fff1e125e133167b77fe40@redchan.it> (raw)
> Steve Litt Wrote:
> The remedies you suggest, if they could even be legally done,
I wonder why you doubt me.
On 2018-09-19 17:09, Steve Litt wrote:
> On Wed, 19 Sep 2018 15:33:58 +0000
> observerofaffairs@redchan.it wrote:
>
>> The CoC will lead only to infighting amongst the contributors, with
>> this new weapon wielded firmly in all participants hands.
>
> You've made your point. Now stop it. The remedies you suggest, if they
> could even be legally done, would hobble the Linux Kernel project, to
> the great delight of Google, Microsoft and Apple. Long observation of
> people resenting CoCs is they want the right to speak cruelly to
> individuals and speak cruelly about groups of people, those groups
> having nothing to do with the list's core foundation (Linux sans
> systemd, in our case). The person continuing to use terminology, having
> nothing to do with the core foundation of the mailing list, that others
> ask them not to use, has a real problem, and it's not the list's duty
> to help with that problem. The project is probably better off without
> the person --- his or her priorities are just plain wrong.
>
> Your posts are offtopic. You've made your point. Please stop now.
>
> SteveT
>
> Steve Litt
> September 2018 featured book: Quit Joblessness: Start Your Own Business
> http://www.troubleshooters.com/startbiz
> _______________________________________________
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
reply other threads:[~2018-09-20 4:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22625a1ca4fff1e125e133167b77fe40@redchan.it \
--to=unconditionedwitness@redchan.it \
--cc=bkuhn@sfconservancy.org \
--cc=blukashev@sempervictus.com \
--cc=bruce@perens.com \
--cc=debian-ctte@lists.debian.org \
--cc=debian-user@lists.debian.org \
--cc=dng@lists.dyne.org \
--cc=editor@lwn.net \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moglen@columbia.edu \
--cc=rms@gnu.org \
--cc=torvalds@osdl.org \
/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.