Linux Kernel Summit discussions
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Bird, Timothy" <Tim.Bird@sony.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors
Date: Mon, 8 Oct 2018 17:43:39 +0200	[thread overview]
Message-ID: <CAMuHMdUckOoFTMN9jH1NPWNcNm0o62w7PtJGF7sa37_1_kceKg@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVmz-ZF+ypp4WEkW6txxjw66DTb5PRsSGPsUfBqT+NbMQ@mail.gmail.com>

On Mon, Oct 8, 2018 at 4:30 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> FTR, I've submitted my patch earlier today, too:
> https://github.com/ContributorCovenant/contributor_covenant/issues/610

Will be clarified in the (external-to-Linux) FAQ.

Quoting Coraline: "However, any adopting project is free to modify the document
according to the license."

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

  reply	other threads:[~2018-10-08 15:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-07  8:51 [Ksummit-discuss] [PATCH] code-of-conduct: Remove explicit list of discrimination factors Geert Uytterhoeven
2018-10-07 11:35 ` Josh Triplett
2018-10-07 17:18   ` Laurent Pinchart
2018-10-08  2:29     ` Josh Triplett
2018-10-08 14:12       ` Tim.Bird
2018-10-08 14:27         ` Laurent Pinchart
2018-10-08 14:36           ` Tim.Bird
2018-10-08 14:30         ` Geert Uytterhoeven
2018-10-08 15:43           ` Geert Uytterhoeven [this message]
2018-10-08  8:55   ` Geert Uytterhoeven
2018-10-08 12:02   ` Mark Brown
2018-10-08 15:42   ` Alan Cox
2018-10-08 16:14     ` Josh Triplett
2018-10-10 20:55 ` Frank Rowand
2018-10-10 21:15   ` Arnaldo Carvalho de Melo
2018-10-10 22:16   ` Josh Triplett
     [not found]     ` <20181010223319.GA31256@thyrsus.com>
2018-10-10 23:35       ` Frank Rowand
  -- strict thread matches above, loose matches on Subject: below --
2018-10-17  7:19 Geert Uytterhoeven
2018-10-17  9:13 ` Josh Triplett
2018-10-17  9:31   ` Geert Uytterhoeven
2018-10-17 13:32     ` Guenter Roeck
2018-10-17 15:22       ` Josh Triplett
2018-10-17 15:21     ` Josh Triplett
2018-10-17 15:49       ` James Bottomley
2018-10-17 16:00         ` Josh Triplett
2018-10-17 18:36       ` Mark Brown
2018-10-17 13:45   ` Guenter Roeck
2018-10-17 16:18   ` Joe Perches
2018-10-22 21:06 ` Pavel Machek

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=CAMuHMdUckOoFTMN9jH1NPWNcNm0o62w7PtJGF7sa37_1_kceKg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=Tim.Bird@sony.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 read-only IMAP folder(s) and NNTP newsgroup(s).