linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Дмитрий Леонтьев" <dm.leontiev7@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Maybe a copyright attack on linux
Date: Wed, 26 Sep 2018 11:30:29 -0400	[thread overview]
Message-ID: <20180926153029.GF3321@thunk.org> (raw)
In-Reply-To: <CA+JonM0_4GSeQ5veX3aDjJ_RBoL065YLNFMuyVftQBn-pCcA=A@mail.gmail.com>

On Wed, Sep 26, 2018 at 05:55:18PM +0300, Дмитрий Леонтьев wrote:
> Or: "Why you should not use "kill switch" option proposed by smdy to
> protest against CoC"
> 
> Hello.
> 
> I'm neither a great software developer nor a lawyer, but I'm not a
> novice and I'm very annoyed whan I see this:
> 
> https://woww.reddit.com/r/programming/comments/9iqr3u/linux_developers_threaten_to_pull_kill_switch/

Dmitry,

Before you worry overmuch, I suggest you take a look at the people who
are the claimed "linux developers" who are so "threatening" and see
how many commits (if any at all) they actually have contributed to he
Linux sources.

There are a lot of people who are not members of the Linux kernel
development community that have been contributing a huge amount of
noise on both sides of the controversy, both pro- and anti- CoC.

My view is that this noise is not at all helpful, and they have their
own agenda which they are trying to promote.  A handy-dandy command if
you have the git tree for the kernel downloaded is:

	git log --author=user@example.com

Best regards,

						- Ted

  reply	other threads:[~2018-09-26 15:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 14:55 Maybe a copyright attack on linux Дмитрий Леонтьев
2018-09-26 15:30 ` Theodore Y. Ts'o [this message]
2018-10-07 17:48   ` Pavel Machek

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=20180926153029.GF3321@thunk.org \
    --to=tytso@mit.edu \
    --cc=dm.leontiev7@gmail.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).