From: Geert Uytterhoeven <geert@linux-m68k.org>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
ksummit-discuss@lists.linuxfoundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] code-of-conduct: Add back the TAB as the central reporting point
Date: Thu, 11 Oct 2018 08:50:20 +0200 [thread overview]
Message-ID: <CAMuHMdVFpaJf-omEXUGjBv6E_4aXoXWT0QRQ138A+9Zcjv97kQ@mail.gmail.com> (raw)
In-Reply-To: <20181010211313.5a63ce6f@alans-desktop>
On Wed, Oct 10, 2018 at 10:14 PM Alan Cox <gnomes@lxorguk.ukuu.org.uk> wrote:
> 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 above change:
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2018-10-11 6:50 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 [this message]
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
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=CAMuHMdVFpaJf-omEXUGjBv6E_4aXoXWT0QRQ138A+9Zcjv97kQ@mail.gmail.com \
--to=geert@linux-m68k.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 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).