qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Fam Zheng <famz@redhat.com>,
	qemu-devel@nongnu.org, Alexandre Derumier <aderumier@odiso.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCHv5] add qemu-img convert -n option (skip target volume creation)
Date: Fri, 30 Aug 2013 12:55:29 -0600	[thread overview]
Message-ID: <5220EAA1.8010301@redhat.com> (raw)
In-Reply-To: <2912C057-823A-4935-B8CE-76E47B8CD8B3@alex.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On 08/30/2013 12:13 PM, Alex Bligh wrote:

>>> +# test of qemu-img convert -n - convert without creation
>>> +#
>>> +# Copyright (C) 2009 Red Hat, Inc.
> 
>> Where have you been the last 4 years?  I could understand a range of
>> years, if this test borrows significantly from another file that old,
>> but I suspect that just 2013 is probably more accurate.
> 
> I've been not at Redhat for any of it!
> 
> I wasn't too sure what to do with the copyright string. The body of
> the code was copied from another test (058 if I remember rightly)
> which had the above copyright string which is presumably that old.

If so, and if I reviewed that patch, shame on me for not noticing the
stale year on that test :)

> Redhat don't have any copyright in the stuff I added so there is
> no (c) Redhat newer than (presumably) 2009 (I'm presuming qemu
> doesn't require contributor assignment). My copyright would be 2013.

Your own work is non-trivial - by virtue of the fact that you list:

+owner=alex@alex.org.uk

you are stating that there is enough new content comprising this test
that you feel comfortable being listed as the point of contact for the file.

> But removing Redhat's (c) or altering it did not seem right.

Indeed, since you are copying a substantial amount of template from Red
Hat's copyright.

> 
> I'm really not bothered about having my own string in there
> particularly for such a meagre bit of code, but I suppose most
> accurate would be:
> 
>   (c) 2009 Red Hat, Inc.
>   (c) 2013 Alex Bligh

Yes, that looks like the best approach.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-08-30 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  9:12 [Qemu-devel] [PATCHv5] add qemu-img convert -n option (skip target volume creation) Alex Bligh
2013-08-26  9:12 ` Alex Bligh
2013-08-30 17:31   ` Eric Blake
2013-08-30 18:13     ` Alex Bligh
2013-08-30 18:55       ` Eric Blake [this message]
2013-08-30 19:22         ` Alex Bligh

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=5220EAA1.8010301@redhat.com \
    --to=eblake@redhat.com \
    --cc=aderumier@odiso.com \
    --cc=alex@alex.org.uk \
    --cc=aliguori@us.ibm.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).