From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v2 2/4] qapi: Create module 'control'
Date: Wed, 29 Jan 2020 11:17:00 +0100 [thread overview]
Message-ID: <20200129101700.GB5690@linux.fritz.box> (raw)
In-Reply-To: <87sgjy1txs.fsf@dusky.pond.sub.org>
Am 29.01.2020 um 10:41 hat Markus Armbruster geschrieben:
> Kevin Wolf <kwolf@redhat.com> writes:
>
> > Am 29.01.2020 um 09:35 hat Markus Armbruster geschrieben:
> >> Kevin Wolf <kwolf@redhat.com> writes:
> >>
> >> > misc.json contains definitions that are related to the system emulator,
> >> > so it can't be used for other tools like the storage daemon. This patch
> >> > moves basic functionality that is shared between all tools (and mostly
> >> > related to the monitor itself) into a new control.json, which could be
> >> > used in tools as well.
> >> >
> >> > Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> >> > ---
> >> > qapi/control.json | 218 +++++++++++++++++++++++++++++++++++++
> >> > qapi/misc.json | 212 ------------------------------------
> >> > qapi/qapi-schema.json | 1 +
> >> > monitor/monitor-internal.h | 1 +
> >> > monitor/hmp-cmds.c | 1 +
> >> > monitor/misc.c | 1 +
> >> > monitor/qmp-cmds.c | 1 +
> >> > monitor/qmp.c | 2 +-
> >> > tests/qtest/qmp-test.c | 2 +-
> >> > ui/gtk.c | 1 +
> >> > qapi/Makefile.objs | 6 +-
> >> > 11 files changed, 229 insertions(+), 217 deletions(-)
> >> > create mode 100644 qapi/control.json
> >> >
> >> > diff --git a/qapi/control.json b/qapi/control.json
> >> > new file mode 100644
> >> > index 0000000000..a82a18da1a
> >> > --- /dev/null
> >> > +++ b/qapi/control.json
> >> > @@ -0,0 +1,218 @@
> >> > +# -*- Mode: Python -*-
> >> > +#
> >> > +
> >>
> >> Let's add a copyright notice:
> >>
> >> # Copyright (C) 2011-2020 Red Hat, Inc.
> >> #
> >> # This work is licensed under the terms of the GNU GPL, version 2 or later.
> >> # See the COPYING file in the top-level directory.
> >
> > I'm not adding anything new, but just moving code from a file that
> > doesn't have a copyright notice. In fact, almost none of the schema
> > files have a copyright notice. I'm not comfortable adding legal
> > assertions without verifying that they are correct, and certainly not as
> > a side-effect of a code movement patch. This would be an unrelated
> > change.
> >
> > I suggest that we leave this patch as is, and if you think copyright
> > notices should be added, the correct information can be tracked down
> > and added consistently for all schema files in a separate series.
>
> There is nothing to be tracked down. Anything that lacks an explicit
> copyright notice is under GPLv2+, as per LICENSE.
The copyright holders should be tracked down rather than just putting
"Red Hat" there, which is most likely wrong. Not that copyright notices
anywhere else are much more complete, but they tend to be correct at
least when they are added (i.e. usually when the file is created), so
not updating them is the fault of the copyright holders that are
missing in the notice.
But anyway, it's unrelated to this patch in either case.
Kevin
next prev parent reply other threads:[~2020-01-29 10:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 17:52 [PATCH v2 0/4] monitor: Refactoring in preparation for qemu-storage-daemon Kevin Wolf
2020-01-28 17:52 ` [PATCH v2 1/4] monitor: Move monitor option parsing to monitor/monitor.c Kevin Wolf
2020-01-29 6:06 ` Markus Armbruster
2020-01-28 17:52 ` [PATCH v2 2/4] qapi: Create module 'control' Kevin Wolf
2020-01-29 8:35 ` Markus Armbruster
2020-01-29 9:09 ` Kevin Wolf
2020-01-29 9:41 ` Markus Armbruster
2020-01-29 10:17 ` Kevin Wolf [this message]
2020-01-28 17:52 ` [PATCH v2 3/4] monitor: Create monitor/qmp-cmds-control.c Kevin Wolf
2020-01-29 9:09 ` Markus Armbruster
2020-01-28 17:52 ` [PATCH v2 4/4] monitor: Move qmp_query_qmp_schema to qmp-cmds-control.c Kevin Wolf
2020-01-29 9:11 ` Markus Armbruster
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=20200129101700.GB5690@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).