From: Jonathan Corbet <corbet@lwn.net>
To: Kristen Carlson Accardi <kristen@linux.intel.com>,
linux-doc@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kristen Carlson Accardi <kristen@linux.intel.com>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices
Date: Thu, 29 Sep 2022 13:15:51 -0600 [thread overview]
Message-ID: <871qruhtzs.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220926211149.2278214-1-kristen@linux.intel.com>
Kristen Carlson Accardi <kristen@linux.intel.com> writes:
> The Code of Conduct interpretation does not reflect the current
> practices of the CoC committee or the TAB. Update the documentation
> to remove references to initial committees and boot strap periods
> since it is past that time, and note that the this document
> does serve as the documentation for the CoC committee processes.
>
> Signed-off-by: Kristen Carlson Accardi <kristen@linux.intel.com>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> .../code-of-conduct-interpretation.rst | 24 ++++++++++---------
> 1 file changed, 13 insertions(+), 11 deletions(-)
I've applied this, thanks.
jon
prev parent reply other threads:[~2022-09-29 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 21:11 [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices Kristen Carlson Accardi
2022-09-26 23:12 ` Jonathan Corbet
2022-09-27 15:59 ` Kristen Carlson Accardi
2022-09-27 16:03 ` Jonathan Corbet
2022-09-27 8:19 ` Bagas Sanjaya
2022-09-27 8:22 ` Greg Kroah-Hartman
2022-09-27 8:27 ` Bagas Sanjaya
2022-09-27 8:43 ` Greg Kroah-Hartman
2022-09-27 12:08 ` Bagas Sanjaya
2022-09-27 8:30 ` Bagas Sanjaya
2022-09-29 19:15 ` Jonathan Corbet [this message]
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=871qruhtzs.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kristen@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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