From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: corbet@lwn.net, conduct@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, jlee@linuxfoundation.org,
stable@vger.kernel.org
Subject: Re: [PATCH] docs: update mediator contact information in CoC doc
Date: Tue, 11 Oct 2022 20:31:48 +0200 [thread overview]
Message-ID: <Y0W2lKIoYDpbJ+LF@kroah.com> (raw)
In-Reply-To: <20221011171417.34286-1-skhan@linuxfoundation.org>
On Tue, Oct 11, 2022 at 11:14:17AM -0600, Shuah Khan wrote:
> Update mediator contact information in CoC interpretation document.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
> Documentation/process/code-of-conduct-interpretation.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/code-of-conduct-interpretation.rst b/Documentation/process/code-of-conduct-interpretation.rst
> index 4f8a06b00f60..43da2cc2e3b9 100644
> --- a/Documentation/process/code-of-conduct-interpretation.rst
> +++ b/Documentation/process/code-of-conduct-interpretation.rst
> @@ -51,7 +51,7 @@ the Technical Advisory Board (TAB) or other maintainers if you're
> uncertain how to handle situations that come up. It will not be
> considered a violation report unless you want it to be. If you are
> uncertain about approaching the TAB or any other maintainers, please
> -reach out to our conflict mediator, Joanna Lee <joanna.lee@gesmer.com>.
> +reach out to our conflict mediator, Joanna Lee <jlee@linuxfoundation.org>.
>
> In the end, "be kind to each other" is really what the end goal is for
> everybody. We know everyone is human and we all fail at times, but the
> --
> 2.34.1
>
Thanks, I'll queue this up after -rc1 is out.
greg k-h
prev parent reply other threads:[~2022-10-11 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 17:14 Shuah Khan
2022-10-11 18:31 ` Greg KH [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=Y0W2lKIoYDpbJ+LF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=conduct@kernel.org \
--cc=corbet@lwn.net \
--cc=jlee@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®