[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jul 2020 09:37:27 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mike Rapoport <rppt@...ux.ibm.com>
Cc: Kees Cook <keescook@...omium.org>,
ksummit <ksummit-discuss@...ts.linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
tech-board-discuss@...ts.linuxfoundation.org,
Andy Lutomirski <luto@...capital.net>, Chris Mason <clm@...clm>
Subject: Re: [Tech-board-discuss] [Ksummit-discuss] [PATCH] CodingStyle:
Inclusive Terminology
On Tue, 7 Jul 2020 09:49:21 +0300
Mike Rapoport <rppt@...ux.ibm.com> wrote:
> > But that's all fine. The change is easy to do and is more descriptive
> > even if I can't find terms that don't collide with my internal grammar
> > checker. ;)
>
> How about yeslist and nolist? ;-)
I was thinking good-list / bad-list.
/me that has been doing a lot of git bisect lately...
-- Steve
Powered by blists - more mailing lists