From: Josh Triplett <josh@joshtriplett.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ksummit-discuss@lists.linuxfoundation.org, tomi.valkeinen@iki.fi
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Wed, 17 Oct 2018 08:22:34 -0700 [thread overview]
Message-ID: <20181017152234.GB17531@localhost> (raw)
In-Reply-To: <1a51fc4c-882c-59ef-7497-262e595af10e@roeck-us.net>
On Wed, Oct 17, 2018 at 06:32:36AM -0700, Guenter Roeck wrote:
> One could consider adding something like "discrimination factors such as",
> or maybe "or any other discrimination factors not listed here" to the
> original text. Or a simple "regardless of, for example, ...".
These sound like perfectly reasonable ways to address this. Please
consider submitting a patch upstream based on this reasoning.
next prev parent reply other threads:[~2018-10-17 15:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 7:19 [PATCH] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-10-17 9:13 ` [Ksummit-discuss] " Josh Triplett
2018-10-17 9:31 ` Geert Uytterhoeven
2018-10-17 13:32 ` Guenter Roeck
2018-10-17 15:22 ` Josh Triplett [this message]
2018-10-17 15:21 ` Josh Triplett
2018-10-17 15:49 ` James Bottomley
2018-10-17 16:00 ` Josh Triplett
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
-- strict thread matches above, loose matches on Subject: below --
2018-10-07 8:51 Geert Uytterhoeven
2018-10-07 11:35 ` [Ksummit-discuss] " Josh Triplett
2018-10-07 17:18 ` Laurent Pinchart
2018-10-08 2:29 ` Josh Triplett
2018-10-08 14:12 ` Tim.Bird
2018-10-08 14:27 ` Laurent Pinchart
2018-10-08 14:36 ` Tim.Bird
2018-10-08 14:30 ` Geert Uytterhoeven
2018-10-08 15:43 ` Geert Uytterhoeven
2018-10-08 8:55 ` Geert Uytterhoeven
2018-10-08 12:02 ` Mark Brown
2018-10-08 15:42 ` Alan Cox
2018-10-08 16:14 ` Josh Triplett
2018-10-10 20:55 ` Frank Rowand
2018-10-10 21:15 ` [Ksummit-discuss] " Arnaldo Carvalho de Melo
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
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=20181017152234.GB17531@localhost \
--to=josh@joshtriplett.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=geert@linux-m68k.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=tomi.valkeinen@iki.fi \
/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).