From: "Luck, Tony" <tony.luck@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>, Dave Airlie <airlied@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
LKML <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Mon, 8 Oct 2018 17:05:58 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D409730@ORSMSX107.amr.corp.intel.com> (raw)
In-Reply-To: <20181007225613.GZ32577@ZenIV.linux.org.uk>
On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote:
> This isn't a legally binding license or anything, but departing from
> the upstream wording makes it tricker to merge new upstream versions
> if they are considered appropriate.
The whole document is under 500 words, if we can manage merges of tens
of thousands of lines of code, this should be pretty easy by comparison.
Making it difficult to merge new upstream versions could also be considered
a positive thing. Given the outcry about this version appearing with no
community discussion, I think folks will also be unhappy about finding some
future merge that just says "Update CoC to upstream 1.5".
-Tony
WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>, Dave Airlie <airlied@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
LKML <linux-kernel@vger.kernel.org>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: RE: [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses
Date: Mon, 8 Oct 2018 17:05:58 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D409730@ORSMSX107.amr.corp.intel.com> (raw)
In-Reply-To: <20181007225613.GZ32577@ZenIV.linux.org.uk>
On Mon, Oct 08, 2018 at 08:25:35AM +1000, Dave Airlie wrote:
> This isn't a legally binding license or anything, but departing from
> the upstream wording makes it tricker to merge new upstream versions
> if they are considered appropriate.
The whole document is under 500 words, if we can manage merges of tens
of thousands of lines of code, this should be pretty easy by comparison.
Making it difficult to merge new upstream versions could also be considered
a positive thing. Given the outcry about this version appearing with no
community discussion, I think folks will also be unhappy about finding some
future merge that just says "Update CoC to upstream 1.5".
-Tony
next prev parent reply other threads:[~2018-10-08 17:06 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 21:35 [Ksummit-discuss] [PATCH 0/2] code of conduct fixes James Bottomley
2018-10-06 21:35 ` James Bottomley
2018-10-06 21:36 ` [Ksummit-discuss] [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email addresses James Bottomley
2018-10-06 21:36 ` James Bottomley
2018-10-07 8:25 ` [Ksummit-discuss] " Geert Uytterhoeven
2018-10-07 8:25 ` Geert Uytterhoeven
2018-10-07 15:25 ` Shuah Khan
2018-10-07 15:25 ` Shuah Khan
2018-10-07 9:04 ` Daniel Vetter
2018-10-07 9:04 ` Daniel Vetter
2018-10-07 9:54 ` Hannes Reinecke
2018-10-07 15:29 ` James Bottomley
2018-10-08 19:49 ` Mauro Carvalho Chehab
2018-10-08 19:49 ` Mauro Carvalho Chehab
2018-10-07 17:53 ` Guenter Roeck
2018-10-07 22:25 ` Dave Airlie
2018-10-07 22:25 ` Dave Airlie
2018-10-07 22:56 ` Al Viro
2018-10-07 23:02 ` Al Viro
2018-10-07 23:37 ` Dave Airlie
2018-10-08 10:14 ` Mark Brown
2018-10-08 10:14 ` Mark Brown
2018-10-08 19:32 ` Mauro Carvalho Chehab
2018-10-08 19:32 ` Mauro Carvalho Chehab
2018-10-08 17:05 ` Luck, Tony [this message]
2018-10-08 17:05 ` Luck, Tony
2018-10-08 14:08 ` James Bottomley
2018-10-10 16:36 ` Pavel Machek
2018-10-10 16:36 ` Pavel Machek
2018-10-08 15:20 ` Josh Triplett
2018-10-08 15:20 ` Josh Triplett
2018-10-08 15:30 ` James Bottomley
2018-10-08 19:23 ` Mauro Carvalho Chehab
2018-10-08 19:23 ` Mauro Carvalho Chehab
2018-10-08 19:57 ` Josh Triplett
2018-10-09 10:55 ` Mark Brown
2018-10-09 18:29 ` Rainer Fiebig
2018-10-09 18:56 ` Josh Triplett
2018-10-09 19:38 ` Laurent Pinchart
2018-10-09 19:38 ` Laurent Pinchart
2018-10-09 19:44 ` James Bottomley
2018-10-10 7:22 ` Rainer Fiebig
2018-10-10 5:52 ` Rainer Fiebig
2018-10-10 7:08 ` Rainer Fiebig
2018-10-08 19:24 ` Mauro Carvalho Chehab
2018-10-08 19:24 ` Mauro Carvalho Chehab
2018-10-10 20:48 ` Frank Rowand
2018-10-06 21:37 ` [Ksummit-discuss] [PATCH 2/2] code-of-conduct: Strip the enforcement paragraph pending community discussion James Bottomley
2018-10-06 21:37 ` James Bottomley
2018-10-06 21:43 ` [Ksummit-discuss] " Tim.Bird
2018-10-06 21:43 ` Tim.Bird
2018-10-07 3:33 ` James Bottomley
2018-10-08 13:51 ` Tim.Bird
2018-10-08 13:51 ` Tim.Bird
2018-10-08 14:09 ` James Bottomley
2018-10-08 17:58 ` Tim.Bird
2018-10-08 17:58 ` Tim.Bird
2018-10-08 18:11 ` James Bottomley
2018-10-08 18:54 ` Tim.Bird
2018-10-08 18:54 ` Tim.Bird
2018-10-08 15:03 ` jonsmirl
2018-10-08 15:03 ` jonsmirl
2018-10-08 15:37 ` Alan Cox
2018-10-08 15:37 ` Alan Cox
2018-10-11 7:42 ` Dan Carpenter
2018-10-07 15:32 ` Shuah Khan
2018-10-07 15:32 ` Shuah Khan
2018-10-07 17:56 ` Guenter Roeck
2018-10-07 19:51 ` Geert Uytterhoeven
2018-10-07 19:51 ` Geert Uytterhoeven
2018-10-08 18:15 ` Chris Mason
2018-10-08 18:15 ` Chris Mason
2018-10-08 19:04 ` [Ksummit-discuss] " Josh Triplett
2018-10-08 20:23 ` Mauro Carvalho Chehab
2018-10-08 20:23 ` Mauro Carvalho Chehab
2018-10-10 15:53 ` Alan Cox
2018-10-10 15:53 ` Alan Cox
2018-10-10 17:19 ` Mauro Carvalho Chehab
2018-10-10 17:19 ` Mauro Carvalho Chehab
2018-10-10 20:09 ` Alan Cox
2018-10-10 20:09 ` Alan Cox
2018-10-10 20:30 ` Mauro Carvalho Chehab
2018-10-10 20:30 ` Mauro Carvalho Chehab
2018-10-10 20:32 ` Dave Airlie
2018-10-07 17:11 ` [Ksummit-discuss] [PATCH 0/2] code of conduct fixes Daniel Vetter
2018-10-07 17:11 ` Daniel Vetter
2018-10-07 17:40 ` James Bottomley
2018-10-07 17:50 ` jonsmirl
2018-10-07 17:50 ` jonsmirl
2018-10-07 17:52 ` Daniel Vetter
2018-10-10 16:12 ` Pavel Machek
2018-10-10 16:12 ` Pavel Machek
2018-10-10 16:25 ` Randy Dunlap
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=3908561D78D1C84285E8C5FCA982C28F7D409730@ORSMSX107.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=airlied@gmail.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.