All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point
Date: Wed, 10 Oct 2018 23:30:39 -0300	[thread overview]
Message-ID: <20181010233039.6ab78374@coco.lan> (raw)
In-Reply-To: <20181010211313.5a63ce6f@alans-desktop>

Em Wed, 10 Oct 2018 21:13:13 +0100
Alan Cox <gnomes@lxorguk.ukuu.org.uk> escreveu:

> On Wed, 10 Oct 2018 13:10:30 -0700
> > +appropriate to the circumstances. The TAB is obligated to maintain
> > +confidentiality with regard to the reporter of an incident.  
> 
> I would add (except where required by law.)

With the proposed change by Alan, you can add my:
	Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>

Thanks,
Mauro

  reply	other threads:[~2018-10-11  2:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 20:07 [Ksummit-discuss] [PATCH v2 0/3] code of conduct fixes James Bottomley
2018-10-10 20:07 ` James Bottomley
2018-10-10 20:08 ` [Ksummit-discuss] [PATCH v2 1/3] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-10 20:08   ` James Bottomley
2018-10-10 22:17   ` [Ksummit-discuss] " Eric W. Biederman
2018-10-10 22:17     ` Eric W. Biederman
2018-10-11  2:33   ` Mauro Carvalho Chehab
2018-10-11  2:33     ` Mauro Carvalho Chehab
2018-10-15 20:58   ` Kees Cook
2018-10-15 20:58     ` Kees Cook
2018-10-10 20:09 ` [Ksummit-discuss] [PATCH v2 2/3] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-10 20:09   ` James Bottomley
2018-10-10 21:04   ` [Ksummit-discuss] " Luck, Tony
2018-10-10 21:04     ` Luck, Tony
2018-10-10 21:19     ` James Bottomley
2018-10-10 21:19       ` James Bottomley
2018-10-10 21:28       ` Luck, Tony
2018-10-10 21:28         ` Luck, Tony
2018-10-15 21:02     ` Kees Cook
2018-10-15 21:02       ` Kees Cook
2018-10-11  2:37   ` Mauro Carvalho Chehab
2018-10-11  2:37     ` Mauro Carvalho Chehab
2018-10-10 20:10 ` [Ksummit-discuss] [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point James Bottomley
2018-10-10 20:10   ` James Bottomley
2018-10-10 20:13   ` [Ksummit-discuss] " Alan Cox
2018-10-10 20:13     ` Alan Cox
2018-10-11  2:30     ` Mauro Carvalho Chehab [this message]
2018-10-11  6:50     ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-11  6:50       ` Geert Uytterhoeven
2018-10-10 21:04   ` [Ksummit-discuss] " Konrad Rzeszutek Wilk
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:23   ` Eric W. Biederman
2018-10-10 23:41   ` Al Viro
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  3:11       ` Mauro Carvalho Chehab
2018-10-11 10:43   ` Rainer Fiebig
2018-10-11  6:39 ` Tomi Valkeinen

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=20181010233039.6ab78374@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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 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.