From: Eric Blake <eblake@redhat.com>
To: David Kiarie <davidkiarie4@gmail.com>, qemu-devel@nongnu.org
Cc: alexaltea123@gmail.com, jan.kiszka@siemens.com,
peterx@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/1] snip my name and email
Date: Thu, 21 Feb 2019 10:05:40 -0600 [thread overview]
Message-ID: <aac6b5d0-ecdd-577c-5b38-8c875ea1dffc@redhat.com> (raw)
In-Reply-To: <20190221155359.8247-1-davidkiarie4@gmail.com>
On 2/21/19 9:53 AM, David Kiarie wrote:
> the occurrence of my name and email on the files below may have led to
> some confusion in the reporting of a few recent bugs.
>
> i have therefore choosen to snip it.
Dropping an email from the copyright line makes sense; dropping the
Copyright declaration altogether is a bit odd (the GPL works only in
tandem with a copyright assertion) - but as you are the author of the
line and copyright holder of your contributions, I am not in a position
to say you are wrong in removing it, only that it looks odd.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-02-21 16:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 15:53 [Qemu-devel] [PATCH 0/1] snip my name and email David Kiarie
2019-02-21 15:53 ` [Qemu-devel] [PATCH 1/1] hw/i386: " David Kiarie
2019-02-21 16:19 ` Daniel P. Berrangé
2019-02-21 16:54 ` David Kiarie
2019-02-21 16:05 ` Eric Blake [this message]
2019-02-21 16:09 ` [Qemu-devel] [PATCH 0/1] " Jan Kiszka
2019-02-21 16:48 ` Markus Armbruster
2019-02-21 16:52 ` Jan Kiszka
2019-02-21 16:57 ` David Kiarie
2019-02-21 17:13 ` Markus Armbruster
2019-02-21 17:35 ` Philippe Mathieu-Daudé
2019-02-21 17:42 ` David Kiarie
2019-02-21 20:47 ` David Kiarie
2019-02-27 18:02 ` 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=aac6b5d0-ecdd-577c-5b38-8c875ea1dffc@redhat.com \
--to=eblake@redhat.com \
--cc=alexaltea123@gmail.com \
--cc=davidkiarie4@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--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).