qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [multiprocess RFC PATCH 36/37] multi-process: add the c


From: Thomas Huth
Subject: Re: [Qemu-devel] [multiprocess RFC PATCH 36/37] multi-process: add the concept description to docs/devel/qemu-multiprocess
Date: Thu, 7 Mar 2019 15:53:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0

On 07/03/2019 15.40, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 07, 2019 at 03:21:47PM +0100, Thomas Huth wrote:
>> On 07/03/2019 15.16, Kevin Wolf wrote:
>>> Am 07.03.2019 um 09:14 hat Thomas Huth geschrieben:
>>>> On 07/03/2019 08.22, address@hidden wrote:
>>>>> From: Elena Ufimtseva <address@hidden>
>>>>>
>>>>> TODO: Make relevant changes to the doc.
>>>>>
>>>>> Signed-off-by: John G Johnson <address@hidden>
>>>>> Signed-off-by: Elena Ufimtseva <address@hidden>
>>>>> Signed-off-by: Jagannathan Raman <address@hidden>
>>>>> ---
>>>>>  docs/devel/qemu-multiprocess.txt | 1109 
>>>>> ++++++++++++++++++++++++++++++++++++++
>>>>>  1 file changed, 1109 insertions(+)
>>>>>  create mode 100644 docs/devel/qemu-multiprocess.txt
>>>>>
>>>>> diff --git a/docs/devel/qemu-multiprocess.txt 
>>>>> b/docs/devel/qemu-multiprocess.txt
>>>>> new file mode 100644
>>>>> index 0000000..e29c6c8
>>>>> --- /dev/null
>>>>> +++ b/docs/devel/qemu-multiprocess.txt
>>>>> @@ -0,0 +1,1109 @@
>>>>> +/*
>>>>> + * Copyright 2019, Oracle and/or its affiliates. All rights reserved.
>>>>> + *
>>>>> + * Permission is hereby granted, free of charge, to any person obtaining 
>>>>> a copy
>>>>> + * of this software and associated documentation files (the "Software"), 
>>>>> to deal
>>>>> + * in the Software without restriction, including without limitation the 
>>>>> rights
>>>>> + * to use, copy, modify, merge, publish, distribute, sublicense, and/or 
>>>>> sell
>>>>> + * copies of the Software, and to permit persons to whom the Software is
>>>>> + * furnished to do so, subject to the following conditions:
>>>>> + *
>>>>> + * The above copyright notice and this permission notice shall be 
>>>>> included in
>>>>> + * all copies or substantial portions of the Software.
>>>>> + *
>>>>> + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, 
>>>>> EXPRESS OR
>>>>> + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 
>>>>> MERCHANTABILITY,
>>>>> + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT 
>>>>> SHALL
>>>>> + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR 
>>>>> OTHER
>>>>> + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, 
>>>>> ARISING FROM,
>>>>> + * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
>>>>> DEALINGS IN
>>>>> + * THE SOFTWARE.
>>>>> + */
>>>>
>>>> Somehow weird to see such a big license statement talking about
>>>> "software", but which applies to a text file only... Not sure if it is
>>>> an option for you, but maybe one of the Creative Common licenses
>>>> (dual-licensed with the GPLv2+) would be a better fit? E.g. for the QEMU
>>>> website, the content is dual-licensed: https://www.qemu.org/license.html
>>>
>>> While we're talking about licenses, the "All rights reserved." notice is
>>> out of place in a license header that declares that a lot of permissions
>>> are granted. Better to remove it to avoid any ambiguities that could
>>> result from the contradiction. (Applies to the whole series.)
>>
>> Apart from that, it is also not required for other work anymore. See:
>>
>> https://en.wikipedia.org/wiki/All_rights_reserved
> 
> Interesting. Do folks know why the Linux Foundation does it?
> 
> See for example cf0d37aecc06801d4847fb36740da4a5690d9d45 (in the Linux kernel)
> where every change they stamp it with their 'All Rights Reserved'?

No clue why they use it. Seems unnecessary to me. But as always: IANAL

 Thomas



reply via email to

[Prev in Thread] Current Thread [Next in Thread]