All of lore.kernel.org
 help / color / mirror / Atom feed
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: Shuah Khan <skhan@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	LF TAB <tech-board@lists.linux-foundation.org>
Subject: Re: [PATCH] Documentation/CoC: Reflect current CoC interpretation and practices
Date: Tue, 27 Sep 2022 10:03:50 -0600	[thread overview]
Message-ID: <87sfkcolcp.fsf@meer.lwn.net> (raw)
In-Reply-To: <a9a569566c2771621f170d017ce981dcfff2b1e7.camel@linux.intel.com>

Kristen Carlson Accardi <kristen@linux.intel.com> writes:

>> > +neutral third party.  The processes the Code of Conduct committee
>> > will
>> > +use to address reports is varied and will depend on the individual
>
> Eek, I see a small error here - it should either say "The processes the
> Code of Conduct committee will use to address reports are varied"
> OR
> "The process the Code of Conduct committee will use to address reports
> is varied"
>
> Perhaps this can be fixed when it is added to a tree, or let me know if
> you would like another version.

I can tweak it, no worries.

Thanks,

jon

  reply	other threads:[~2022-09-27 16:06 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 [this message]
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

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=87sfkcolcp.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 \
    --cc=tech-board@lists.linux-foundation.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.