From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Josh Triplett <josh@joshtriplett.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Mon, 8 Oct 2018 16:42:47 +0100 [thread overview]
Message-ID: <20181008164247.48b60ba7@alans-desktop> (raw)
In-Reply-To: <20181007113514.GA21217@localhost>
> 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.
Alan
WARNING: multiple messages have this Message-ID (diff)
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
ksummit-discuss@lists.linuxfoundation.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Mon, 8 Oct 2018 16:42:47 +0100 [thread overview]
Message-ID: <20181008164247.48b60ba7@alans-desktop> (raw)
In-Reply-To: <20181007113514.GA21217@localhost>
> 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.
Alan
next prev parent reply other threads:[~2018-10-08 15:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 8:51 [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-10-07 8:51 ` Geert Uytterhoeven
2018-10-07 11:35 ` [Ksummit-discuss] " Josh Triplett
2018-10-07 11:35 ` Josh Triplett
2018-10-07 17:18 ` Laurent Pinchart
2018-10-07 17:18 ` Laurent Pinchart
2018-10-08 2:29 ` Josh Triplett
2018-10-08 2:29 ` Josh Triplett
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 12:02 ` Mark Brown
2018-10-08 12:02 ` Mark Brown
2018-10-08 15:42 ` Alan Cox [this message]
2018-10-08 15:42 ` Alan Cox
2018-10-08 16:14 ` Josh Triplett
2018-10-08 16:14 ` Josh Triplett
2018-10-10 20:55 ` Frank Rowand
2018-10-10 20:55 ` Frank Rowand
2018-10-10 21:15 ` [Ksummit-discuss] " Arnaldo Carvalho de Melo
2018-10-10 21:15 ` Arnaldo Carvalho de Melo
2018-10-10 22:16 ` Josh Triplett
2018-10-10 22:16 ` Josh Triplett
2018-10-10 22:33 ` Eric S. Raymond
2018-10-10 23:35 ` Frank Rowand
2018-10-11 8:12 ` Rainer Fiebig
2018-10-11 6:36 ` Tomi Valkeinen
-- strict thread matches above, loose matches on Subject: below --
2018-10-17 7:19 [Ksummit-discuss] " Geert Uytterhoeven
2018-10-17 9:13 ` Josh Triplett
2018-10-17 9:13 ` Josh Triplett
2018-10-17 9:31 ` Geert Uytterhoeven
2018-10-17 9:31 ` Geert Uytterhoeven
2018-10-17 13:32 ` Guenter Roeck
2018-10-17 15:22 ` Josh Triplett
2018-10-17 15:22 ` Josh Triplett
2018-10-17 15:21 ` Josh Triplett
2018-10-17 15:21 ` Josh Triplett
2018-10-17 15:49 ` James Bottomley
2018-10-17 16:00 ` Josh Triplett
2018-10-17 16:00 ` Josh Triplett
2018-10-17 18:36 ` Mark Brown
2018-10-17 18:36 ` Mark Brown
2018-10-17 13:45 ` Guenter Roeck
2018-10-17 16:18 ` Joe Perches
2018-10-22 21:06 ` 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=20181008164247.48b60ba7@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=James.Bottomley@hansenpartnership.com \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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 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.