Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp3771769imm; Mon, 8 Oct 2018 09:14:56 -0700 (PDT) X-Google-Smtp-Source: ACcGV6033zjY/Fz8tzLUc/TciNTkuVMM0dr9+YlhxVGVo+YKK5+6B7FS2EfpC8+yHbijG6R/KBcu X-Received: by 2002:a17:902:780d:: with SMTP id p13-v6mr24679931pll.96.1539015296633; Mon, 08 Oct 2018 09:14:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539015296; cv=none; d=google.com; s=arc-20160816; b=Bym9HU0PHAseVRGHDK2a1o7Tl4nIPE+wfVt+s5Skq0maURY5Gi5vLKy8Tl8QJ7uGv5 qxnTxOy3nJvzY3LqXMk2IH4k+dDNBVVBmk07xcW4cx9e8q+Ge9Ax3k+rrk4snr8qjOlV UGqN5ogg92V5tcNly9w8FkfMDfDoJhuvx2hycP1Y9bJpAUXkNvKdZMwn0tZFTualsK0u hiQpLLZcbCg3w9j+NIEvMAeGSdDMUxt2e1gQuOpDZq6yOXGyXhOUcSgLOtXrYd0PZPEx Y96/mLzQEAy2kiWS6DHBIw3wKQAjDLVnX+TLED02HY+WmG6LJee3C/J5EmaxdXhRbpXB 1bsw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=JaoAbAsqnHyCL6hcszkHSQdqvb5rtZRM/OCW3lf9Jgo=; b=jQNWu3BUtWpXU0+NoCUFgqmrP7YL6Qr1Iaq1kSmZ6b1jdTHsddbZJ0nro/0VXjvtYT PGifyLrPO3rBXYR4qFHHJIXdofvCZLHbdS7NPi/qFrUr1TrR9Js5j6PX2j6EpFM0goR/ WnCcUab9a1exuSP8YDyvXZBrvDW7wY+KdTgoEyG9O8AbhRQvkBFcGuXBK+mF0bOxyggb b93LcYujeFRZBuvDAgOQIWqUakL0AT5Yo/Q8/Ipl5JNATA8KrNFrZZV8tJW99l70lD7F G3HJs9cmu8JmO+JHR+Vo3mlwSypwhT0F18jJR0j0hHS6nVzJ4LTAm9Dd7BlJsD/cRgBZ DtKw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p9-v6si20798481pll.298.2018.10.08.09.14.41; Mon, 08 Oct 2018 09:14:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726445AbeJHX0j (ORCPT + 99 others); Mon, 8 Oct 2018 19:26:39 -0400 Received: from relay6-d.mail.gandi.net ([217.70.183.198]:37851 "EHLO relay6-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726291AbeJHX0j (ORCPT ); Mon, 8 Oct 2018 19:26:39 -0400 X-Originating-IP: 50.39.174.102 Received: from localhost (50-39-174-102.bvtn.or.frontiernet.net [50.39.174.102]) (Authenticated sender: josh@joshtriplett.org) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 4BCE5C000A; Mon, 8 Oct 2018 16:14:06 +0000 (UTC) Date: Mon, 8 Oct 2018 09:14:05 -0700 From: Josh Triplett To: Alan Cox Cc: Geert Uytterhoeven , ksummit-discuss@lists.linuxfoundation.org, James Bottomley , linux-kernel@vger.kernel.org Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors Message-ID: <20181008161404.GA11021@localhost> References: <20181007085102.17795-1-geert@linux-m68k.org> <20181007113514.GA21217@localhost> <20181008164247.48b60ba7@alans-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181008164247.48b60ba7@alans-desktop> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 08, 2018 at 04:42:47PM +0100, Alan Cox wrote: > > In any case, this is not the appropriate place for such patches, any > > more than it's the place for patches to the GPL. > > I disagree. We had the GPLv2 or GPLv3 discussion on the kernel mailing > list. The syscall clarification was discussed on the list. The > EXPORT_SYMBOL and EXPORT_SYMBOL_GPL stuff was discussed on the list. And discussion of this could occur on the list, as well. I said "for such patches", not "for such discussion". And, incidentally, this particular issues has now been addressed upstream. I proposed a change to the FAQ, which has now been merged. See https://www.contributor-covenant.org/faq and https://github.com/ContributorCovenant/contributor_covenant/pull/612 .