From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Smirnov <asmirnov@ilbers.de>, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] meta/classes/base: Fix showdata and liststasks after bitbake update
Date: Thu, 8 Feb 2018 17:18:41 +0100 [thread overview]
Message-ID: <22602343-0c6a-819a-7324-f2047c325ddb@siemens.com> (raw)
In-Reply-To: <7b5c6107-ee95-3e83-b7cf-615122a4c765@siemens.com>
On 2018-02-08 17:13, Jan Kiszka wrote:
> On 2018-02-08 16:47, Alexander Smirnov wrote:
>> On 02/08/2018 06:24 PM, Claudius Heine wrote:
>>> Hi Alex,
>>>
>>> On 02/08/2018 02:55 PM, Alexander Smirnov wrote:
>>>> Hi,
>>>>
>>>> On 02/08/2018 02:26 PM, claudius.heine.ext@siemens.com wrote:
>>>>> From: Claudius Heine <ch@denx.de>
>>>>>
>>>>> Those tasks were broken, this patchs fixes by implementing them similar
>>>>> to how openembedded-core does it.
>>>>>
>>>>
>>>> I see that this code is identical to OE one, do you know which
>>>> copyright it is? If this code is copied from OE, I think it makes
>>>> sense to mention this explicitly in the code.
>>>
>>> Sure, I got it from [1], and this file does not have an own header, so
>>> I suppose its MIT or GPLv2. I don't know if this falls under
>>> 'metadata' or not. Since Isar uses the same licenses, you might know
>>> what exactly is meant by that.
>>>
>>> How are you proposing to name the authors?
>>
>> I see it something like:
>>
>> # Derived from openembedded-core/meta/classes/utility-tasks.bbclass
>>
>> @Jan: do you think we should keep this reference?
>
> It doesn't harm us, I would say.
>
> In general, it would be better for Isar (compared to OE) to have clear
> licensing statements in each file. State-of-the-art is leaving the right
> SPDX-License-Identifier behind.
...which I didn't do either in my recent patches. Will fix and send v2.
How about this pattern:
# SPDX-License-Identifier: MIT
#
# <some optional file description>
#
# This software is a part of ISAR.
# Copyright (c) Siemens AG, 2018
#
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2018-02-08 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 11:26 claudius.heine.ext
2018-02-08 13:55 ` Alexander Smirnov
2018-02-08 15:24 ` Claudius Heine
2018-02-08 15:40 ` Claudius Heine
2018-02-08 15:47 ` Alexander Smirnov
2018-02-08 16:13 ` Jan Kiszka
2018-02-08 16:18 ` Jan Kiszka [this message]
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=22602343-0c6a-819a-7324-f2047c325ddb@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=ch@denx.de \
--cc=isar-users@googlegroups.com \
/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