linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@iki.fi>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
	ksummit-discuss@lists.linuxfoundation.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] code of conduct fixes
Date: Thu, 11 Oct 2018 09:39:45 +0300	[thread overview]
Message-ID: <6b0d5ad6-c76b-8dbf-bd74-de352280e780@iki.fi> (raw)
In-Reply-To: <1539202053.12644.8.camel@HansenPartnership.com>

On 10/10/18 23:07, James Bottomley wrote:
> Resend to show accumulated tags and also to add a third patch listing
> the TAB as the reporting point as a few people seem to want.  If it
> gets the same level of support, I'll send it in with the other two.
> 
> ---
> 
> Previous cover letter:
> 
> 
> We've had several threads discussing potential changes to the code of
> conduct but Mauro is the only person to have proposed an actual patch. 
> In order to move the debate on, I'm presenting two patches, one to fix
> the email problem Mauro identified and the other to strip the
> enforcement section pending community discussion as Shuah suggested.
> 
> I'll take responsibility for collecting any tags people want to add
> (review/ack/sign off, etc) and sending the patch in as a signed pull
> request before 4.19 final if they get enough community support.
> 
> Note, I've sent both patches in as a series to facilitate review and
> discussion, but they are separable if one is looked on with less favour
> than the other.
> 
> It was also a bit unclear which list to send this to, but I finally
> settled on linux-kernel as the catch all and ksummit-discuss since
> that's where most of the current discussion is.  I can add other lists
> as people suggest them.
> 
> James
> 
> ---
> 
> James Bottomley (3):
>   code-of-conduct: Fix the ambiguity about collecting email addresses
>   code-of-conduct: Strip the enforcement paragraph pending community
>     discussion
>   code-of-conduct: Add back the TAB as the central reporting point
> 
>  Documentation/process/code-of-conduct.rst | 13 ++++---------
>  1 file changed, 4 insertions(+), 9 deletions(-)
> 

For the three patches (preferably with Alan's "except where required by
law"):

Acked-by: Tomi Valkeinen <tomi.valkeinen@iki.fi>

Although I think reverting 8a104f8b5867c682 is the best option.

 Tomi

      parent reply	other threads:[~2018-10-11  6:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 20:07 [PATCH v2 0/3] code of conduct fixes James Bottomley
2018-10-10 20:08 ` [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-10 22:17   ` [Ksummit-discuss] " Eric W. Biederman
2018-10-11  2:33   ` Mauro Carvalho Chehab
2018-10-15 20:58   ` Kees Cook
2018-10-10 20:09 ` [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-10 21:04   ` [Ksummit-discuss] " Luck, Tony
2018-10-10 21:19     ` James Bottomley
2018-10-10 21:28       ` Luck, Tony
2018-10-15 21:02     ` Kees Cook
2018-10-11  2:37   ` Mauro Carvalho Chehab
2018-10-10 20:10 ` [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-10 20:13   ` Alan Cox
2018-10-11  2:30     ` [Ksummit-discuss] " Mauro Carvalho Chehab
2018-10-11  6:50     ` Geert Uytterhoeven
2018-10-10 21:04   ` Konrad Rzeszutek Wilk
2018-10-10 23:23 ` [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes Eric W. Biederman
2018-10-10 23:41   ` Al Viro
2018-10-11  0:00   ` James Bottomley
2018-10-11  3:11     ` Mauro Carvalho Chehab
2018-10-11 10:43   ` Rainer Fiebig
2018-10-11  6:39 ` Tomi Valkeinen [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=6b0d5ad6-c76b-8dbf-bd74-de352280e780@iki.fi \
    --to=tomi.valkeinen@iki.fi \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).