From: Eric Blake <eblake@redhat.com>
To: John Bradley <flypie1@yahoo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "John Bradley" <flypie@rocketmail.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Geert Martin Ijewski" <gm.ijewski@web.de>,
"Markus Armbruster" <armbru@redhat.com>,
"Alistair Francis" <alistair.francis@xilinx.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM.
Date: Wed, 17 May 2017 16:55:41 -0500 [thread overview]
Message-ID: <d7324134-4eb5-0ca2-2a13-6fd5c5479b49@redhat.com> (raw)
In-Reply-To: <968647832.156883.1495056309814@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
On 05/17/2017 04:25 PM, John Bradley wrote:
> Well unfortunately Eric. I don't understand your "top posted" slang.
To learn what top-posting is:
http://lmgtfy.com/?q=what+is+top-posting
and why we don't like it on technical lists:
http://www.caliburn.nl/topposting.html
Or more humorously:
A: Yes.
> >Q: Are you sure?
>> >>A: Because it reverses the logical flow of conversation.
>>> >>>Q: Why is top posting frowned upon?
>
> As for his "intent", it is quite irrelevant as I have gone over the code line by line and what every he intended to do, he has succeed, as far as I can tell , in matching you standards, to such an extent that I am happy that
You are correct that the GPL gives us legal rights to use Andrew's code
without his permission. And yes, YOU can fork qemu, and take whatever
GPL patches you want without attribution, and you are probably still
just fine legally (as long as you still abide by the GPL in that you
distribute sources to anyone that has your binary).
But our project rules do not allow us to live by just GPL (in part,
because the license of qemu is sometimes tricky to determine due to a
mix of GPLv2-only code and non-GPL code, even though most new code is
GPLv2+). Also, if we ever had a reason to change license (supposing it
is even possible, although it might require ripping out or
reimplementing portions of the code base), having S-o-b means that we
cannot be accused of applying a license that someone did not agree to.
Therefore, it is easier, pragmatically, even if not legally necessary,
to enforce proper chain of authorship by getting Signed-off-by: tags on
ALL patches, especially where a patch asserts a copyright owner, insofar
as the original copyright owner is still alive and able to assent to the
action. It is not just about legalities, it is also about risk-avoidance.
It may sound like we are being hard-nosed (and so be it), but there's a
reason that we list proper Signed-off-by: rules as our number 1 item on
the SubmitAPatch page.
http://wiki.qemu.org/Contribute/SubmitAPatch
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-05-17 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <684185116.2952708.1495044580181.ref@mail.yahoo.com>
2017-05-17 18:09 ` [Qemu-devel] Add Markus Armbrusters code for Broadcom Perhiperals for ARM John Bradley
2017-05-17 18:27 ` Eric Blake
2017-05-17 18:34 ` John Bradley
2017-05-17 19:11 ` Eric Blake
2017-05-17 20:53 ` John Bradley
2017-05-17 21:15 ` Eric Blake
2017-05-17 21:25 ` John Bradley
2017-05-17 21:55 ` Eric Blake [this message]
2017-05-18 7:47 ` Markus Armbruster
2017-05-18 16:39 ` John Bradley
2017-05-17 19:04 ` John Snow
2017-05-18 1:52 ` Eric Blake
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=d7324134-4eb5-0ca2-2a13-6fd5c5479b49@redhat.com \
--to=eblake@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=flypie1@yahoo.com \
--cc=flypie@rocketmail.com \
--cc=gm.ijewski@web.de \
--cc=lvivier@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@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).