From: Thomas Huth <thuth@redhat.com>
To: "Collin L. Walling" <walling@linux.vnet.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Eric Blake <eblake@redhat.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: alifm@linux.vnet.ibm.com, frankja@linux.vnet.ibm.com,
cohuck@redhat.com, david@redhat.com
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v3 1/8] s390-ccw: update libc
Date: Tue, 16 Jan 2018 16:48:48 +0100 [thread overview]
Message-ID: <e5a8a7a7-676f-1aa9-79b5-651d4494bc84@redhat.com> (raw)
In-Reply-To: <b86618f5-e5cb-8953-508f-e73339b1a475@linux.vnet.ibm.com>
On 16.01.2018 16:32, Collin L. Walling wrote:
> On 01/16/2018 06:07 AM, Christian Borntraeger wrote:
>>
>> On 01/15/2018 06:23 PM, Collin L. Walling wrote:
>>> On 01/15/2018 12:05 PM, Eric Blake wrote:
[...]
>>>> I'm not a lawyer, but generically, the GPL and its variants depend on a
>>>> copyright owner to actually work. You may want to add a copyright
>>>> line.
>>>
>>> I'll have to check on that. I was not the original author of the
>>> libc.h file.
>> I think you can add the normal IBM Copyright statement. (I think all
>> authors could add theirs as well)
>
> "Copyright 2018 IBM Corp."
>
> @Thomas, git shows you as the initial creator of libc.h. Shall I add
> "Copyright 2018 Thomas Huth, Red Hat Inc." in there as well?
Actually, I only moved the functions from s390-ccw.h and sclp.c into
that header file. I just tried to trace who introduced them first, and
it seems like it was Alex who added them. So I guess you should add:
Copyright (c) 2013 Alexander Graf <agraf@suse.de>
to libc.h for that. Sorry that I did not do that right from the start.
Thomas
next prev parent reply other threads:[~2018-01-16 15:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 16:44 [Qemu-devel] [PATCH v3 0/8] Interactive Boot Menu for DASD and SCSI Guests on s390x Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 1/8] s390-ccw: update libc Collin L. Walling
2018-01-15 17:05 ` Eric Blake
2018-01-15 17:23 ` Collin L. Walling
2018-01-16 10:00 ` Thomas Huth
2018-01-16 17:19 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-01-16 11:07 ` Christian Borntraeger
2018-01-16 15:32 ` Collin L. Walling
2018-01-16 15:48 ` Thomas Huth [this message]
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 2/8] s390-ccw: ipl structs for eckd cdl/ldl Collin L. Walling
2018-01-16 12:32 ` Thomas Huth
2018-01-16 15:21 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 3/8] s390-ccw: parse and set boot menu options Collin L. Walling
2018-01-16 12:44 ` Thomas Huth
2018-01-16 15:26 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 4/8] s390-ccw: interactive boot menu for eckd dasd (menu setup) Collin L. Walling
2018-01-16 18:23 ` Thomas Huth
2018-01-16 19:37 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-01-17 6:11 ` Thomas Huth
2018-01-17 12:12 ` Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 5/8] s390-ccw: interactive boot menu for eckd dasd (read stage2 data) Collin L. Walling
2018-01-17 8:38 ` Thomas Huth
2018-01-17 9:12 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2018-01-17 12:29 ` Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 6/8] s390-ccw: interactive boot menu for eckd dasd (print menu) Collin L. Walling
2018-01-17 8:58 ` Thomas Huth
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 7/8] s390-ccw: interactive boot menu for eckd dasd (read input) Collin L. Walling
2018-01-17 10:10 ` Thomas Huth
2018-01-17 13:19 ` [Qemu-devel] [qemu-s390x] " Collin L. Walling
2018-01-15 16:44 ` [Qemu-devel] [PATCH v3 8/8] s390-ccw: interactive boot menu for scsi Collin L. Walling
2018-01-17 10:16 ` Thomas Huth
2018-01-15 16:58 ` [Qemu-devel] [PATCH v3 0/8] Interactive Boot Menu for DASD and SCSI Guests on s390x no-reply
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=e5a8a7a7-676f-1aa9-79b5-651d4494bc84@redhat.com \
--to=thuth@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=walling@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).