On 10/06/18 14:36, James Bottomley wrote:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The current code of
On 10/06/18 14:36, James Bottomley wrote:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The current code of
> > Signed-off-by: James Bottomley
> > ---
> > Documentation/process/code-of-conduct.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/code-of-conduct.rst
> > b/Documentation/process/code-of-conduct.rst
> > index ab7c24b5478c..aa40e34e7785
> > Signed-off-by: James Bottomley
> > ---
> > Documentation/process/code-of-conduct.rst | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/code-of-conduct.rst
> > b/Documentation/process/code-of-conduct.rst
> > index ab7c24b5478c..aa40e34e7785
James Bottomley schrieb:
> On Tue, 2018-10-09 at 22:38 +0300, Laurent Pinchart wrote:
>> Hi Josh,
>>
>> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
>>> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
James Bottomley schrieb:
> On Tue, 2018-10-09 at 22:38 +0300, Laurent Pinchart wrote:
>> Hi Josh,
>>
>> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
>>> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
Josh Triplett schrieb:
> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
>> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
>>> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
The current code of conduct has an ambiguity in the it considers
Josh Triplett schrieb:
> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
>> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
>>> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
The current code of conduct has an ambiguity in the it considers
Laurent Pinchart schrieb:
> Hi Josh,
>
> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
>> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
>>> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley
Laurent Pinchart schrieb:
> Hi Josh,
>
> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
>> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
>>> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley
On Tue, 2018-10-09 at 22:38 +0300, Laurent Pinchart wrote:
> Hi Josh,
>
> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
> > On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> > > Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > > > On Sat, Oct 06, 2018
On Tue, 2018-10-09 at 22:38 +0300, Laurent Pinchart wrote:
> Hi Josh,
>
> On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
> > On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> > > Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > > > On Sat, Oct 06, 2018
Hi Josh,
On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> > Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> >> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> >>> The current code of
Hi Josh,
On Tuesday, 9 October 2018 21:56:23 EEST Josh Triplett wrote:
> On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> > Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> >> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> >>> The current code of
On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing
> > > private
On Tue, Oct 09, 2018 at 08:29:24PM +0200, Rainer Fiebig wrote:
> Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing
> > > private
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers publishing
> > private information such as email addresses unacceptable behaviour. Since
> > the
Am Montag, 8. Oktober 2018, 08:20:44 schrieb Josh Triplett:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers publishing
> > private information such as email addresses unacceptable behaviour. Since
> > the
On Mon, Oct 08, 2018 at 12:57:51PM -0700, Josh Triplett wrote:
> On Mon, Oct 08, 2018 at 04:23:57PM -0300, Mauro Carvalho Chehab wrote:
> > Fully agreed on that. The same argument that we use for GPL 2 only
> > applies here: we should stick with an specific version of this it, in
> > a way that
On Mon, Oct 08, 2018 at 12:57:51PM -0700, Josh Triplett wrote:
> On Mon, Oct 08, 2018 at 04:23:57PM -0300, Mauro Carvalho Chehab wrote:
> > Fully agreed on that. The same argument that we use for GPL 2 only
> > applies here: we should stick with an specific version of this it, in
> > a way that
On Mon, Oct 08, 2018 at 04:23:57PM -0300, Mauro Carvalho Chehab wrote:
> Em Mon, 08 Oct 2018 08:30:20 -0700
> James Bottomley escreveu:
>
> > On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> > > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > > The current code
On Mon, Oct 08, 2018 at 04:23:57PM -0300, Mauro Carvalho Chehab wrote:
> Em Mon, 08 Oct 2018 08:30:20 -0700
> James Bottomley escreveu:
>
> > On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> > > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > > The current code
Em Sun, 07 Oct 2018 08:29:01 -0700
James Bottomley escreveu:
> On Sun, 2018-10-07 at 11:04 +0200, Daniel Vetter wrote:
> > On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> > wrote:
> > >
> > > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > > 2001
> > > From: James
Em Sun, 07 Oct 2018 08:29:01 -0700
James Bottomley escreveu:
> On Sun, 2018-10-07 at 11:04 +0200, Daniel Vetter wrote:
> > On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> > wrote:
> > >
> > > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > > 2001
> > > From: James
Em Mon, 8 Oct 2018 09:37:59 +1000
Dave Airlie escreveu:
> On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
> >
> > 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
Em Mon, 8 Oct 2018 09:37:59 +1000
Dave Airlie escreveu:
> On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
> >
> > 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
Em Sat, 06 Oct 2018 14:36:39 -0700
James Bottomley escreveu:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
>
Em Sat, 06 Oct 2018 14:36:39 -0700
James Bottomley escreveu:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
>
Em Mon, 08 Oct 2018 08:30:20 -0700
James Bottomley escreveu:
> On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing private
Em Mon, 08 Oct 2018 08:30:20 -0700
James Bottomley escreveu:
> On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> > On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > > The current code of conduct has an ambiguity in the it considers
> > > publishing private
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
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
On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers
> > publishing private information such as email addresses unacceptable
> > behaviour. Since the Linux
On Mon, 2018-10-08 at 08:20 -0700, Josh Triplett wrote:
> On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> > The current code of conduct has an ambiguity in the it considers
> > publishing private information such as email addresses unacceptable
> > behaviour. Since the Linux
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> The current code of conduct has an ambiguity in the it considers publishing
> private information such as email addresses unacceptable behaviour. Since
> the Linux kernel collects and publishes email addresses as part of the patch
On Sat, Oct 06, 2018 at 02:36:39PM -0700, James Bottomley wrote:
> The current code of conduct has an ambiguity in the it considers publishing
> private information such as email addresses unacceptable behaviour. Since
> the Linux kernel collects and publishes email addresses as part of the patch
On Mon, 2018-10-08 at 08:25 +1000, Dave Airlie wrote:
> On Sun, 7 Oct 2018 at 07:36, James Bottomley
> wrote:
> >
> > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > 2001
> > From: James Bottomley
> > Date: Sat, 6 Oct 2018 14:21:56 -0700
> > Subject: [PATCH 1/2]
On Mon, 2018-10-08 at 08:25 +1000, Dave Airlie wrote:
> On Sun, 7 Oct 2018 at 07:36, James Bottomley
> wrote:
> >
> > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > 2001
> > From: James Bottomley
> > Date: Sat, 6 Oct 2018 14:21:56 -0700
> > Subject: [PATCH 1/2]
On Mon, Oct 08, 2018 at 09:37:59AM +1000, Dave Airlie wrote:
> On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
> > We can surround it with "explanations" until we get something that more or
> > less fits, but then we'd need to reanalyse them every time an upstream
> > change gets merged. And the
On Mon, Oct 08, 2018 at 09:37:59AM +1000, Dave Airlie wrote:
> On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
> > We can surround it with "explanations" until we get something that more or
> > less fits, but then we'd need to reanalyse them every time an upstream
> > change gets merged. And the
On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
>
> 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.
On Mon, 8 Oct 2018 at 08:56, Al Viro wrote:
>
> 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.
On Sun, Oct 07, 2018 at 11:56:13PM +0100, Al Viro wrote:
> We can surround it with "explanations"
Sorry, "clarifications". Or whatever euphemism you prefer for
exegesis, really...
On Sun, Oct 07, 2018 at 11:56:13PM +0100, Al Viro wrote:
> We can surround it with "explanations"
Sorry, "clarifications". Or whatever euphemism you prefer for
exegesis, really...
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.
Nicely done, that - gotta love the passive voice use.
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.
Nicely done, that - gotta love the passive voice use.
On Sun, 7 Oct 2018 at 07:36, James Bottomley
wrote:
>
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The
On Sun, 7 Oct 2018 at 07:36, James Bottomley
wrote:
>
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The
On 10/06/2018 02:36 PM, James Bottomley wrote:
From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
From: James Bottomley
Date: Sat, 6 Oct 2018 14:21:56 -0700
Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
addresses
The current code of
On 10/06/2018 02:36 PM, James Bottomley wrote:
From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
From: James Bottomley
Date: Sat, 6 Oct 2018 14:21:56 -0700
Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
addresses
The current code of
On Sun, 2018-10-07 at 11:04 +0200, Daniel Vetter wrote:
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
> >
> > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > 2001
> > From: James Bottomley
> > Date: Sat, 6 Oct 2018 14:21:56 -0700
> > Subject: [PATCH 1/2]
On Sun, 2018-10-07 at 11:04 +0200, Daniel Vetter wrote:
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
> >
> > From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00
> > 2001
> > From: James Bottomley
> > Date: Sat, 6 Oct 2018 14:21:56 -0700
> > Subject: [PATCH 1/2]
Hi James,
Thanks for the patch.
On 10/07/2018 02:25 AM, Geert Uytterhoeven wrote:
> Hi James,
>
> Thanks for your patch!
>
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
>> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
>> From: James Bottomley
>> Date:
Hi James,
Thanks for the patch.
On 10/07/2018 02:25 AM, Geert Uytterhoeven wrote:
> Hi James,
>
> Thanks for your patch!
>
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
>> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
>> From: James Bottomley
>> Date:
On 10/7/18 11:04 AM, Daniel Vetter wrote:
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
>>
>> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
>> From: James Bottomley
>> Date: Sat, 6 Oct 2018 14:21:56 -0700
>> Subject: [PATCH 1/2] code-of-conduct: Fix the
On 10/7/18 11:04 AM, Daniel Vetter wrote:
> On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
> wrote:
>>
>> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
>> From: James Bottomley
>> Date: Sat, 6 Oct 2018 14:21:56 -0700
>> Subject: [PATCH 1/2] code-of-conduct: Fix the
On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
wrote:
>
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The
On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
wrote:
>
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about collecting email
> addresses
>
> The
Hi James,
Thanks for your patch!
On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
wrote:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about
Hi James,
Thanks for your patch!
On Sat, Oct 6, 2018 at 11:36 PM James Bottomley
wrote:
> From 4a614e9440148894207bef5bf69e74071baceb3b Mon Sep 17 00:00:00 2001
> From: James Bottomley
> Date: Sat, 6 Oct 2018 14:21:56 -0700
> Subject: [PATCH 1/2] code-of-conduct: Fix the ambiguity about
60 matches
Mail list logo
