From: Chris Krumme <chris.krumme@windriver.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH v2 10/10] vnc: update copyrights for vnc-encoding-tight.c
Date: Tue, 18 May 2010 08:47:47 -0500 [thread overview]
Message-ID: <4BF29A83.8030903@windriver.com> (raw)
In-Reply-To: <4BF297FC.7090403@linux.vnet.ibm.com>
On 05/18/2010 08:37 AM, Anthony Liguori wrote:
> On 05/18/2010 07:49 AM, Corentin Chary wrote:
>> Add missing copyrights in vnc-encoding-tight.c, since the code is
>> mostly inspired from libvncserver/tight.c.
>>
>> Signed-off-by: Corentin Chary<corentincj@iksaif.net>
>> ---
>> vnc-encoding-tight.c | 5 +++++
>> 1 files changed, 5 insertions(+), 0 deletions(-)
>>
>> diff --git a/vnc-encoding-tight.c b/vnc-encoding-tight.c
>> index b836569..0c661a9 100644
>> --- a/vnc-encoding-tight.c
>> +++ b/vnc-encoding-tight.c
>> @@ -1,9 +1,14 @@
>> /*
>> * QEMU VNC display driver: tight encoding
>> *
>> + * From libvncserver/tight.c
>> + * Copyright (C) 1999 AT&T Laboratories Cambridge. All Rights
>> Reserved.
>> + * Copyright (C) 2000, 2001 Const Kaplinsky. All Rights Reserved.
>> + *
>> * Copyright (C) 2006 Anthony Liguori<anthony@codemonkey.ws>
>> * Copyright (C) 2006 Fabrice Bellard
>> * Copyright (C) 2009 Red Hat, Inc
>> + * Copyright (C) 2019 Corentin Chary<corentin.chary@gmail.com>
Maybe the laws are different in our future. 9 years from now this whole
IP issue may be resolved. (or you may want to correct the year also.)
Thanks
Chris
>> *
>> * Permission is hereby granted, free of charge, to any person
>> obtaining a copy
>> * of this software and associated documentation files (the
>> "Software"), to deal
>
> This should come earlier in the series and also needs to carry a LICENSE.
>
> If it's truly under 'All Rights Reserved', then we cannot incorporate
> this code into QEMU.
>
> Regards,
>
> Anthony Liguori
>
next prev parent reply other threads:[~2010-05-18 13:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 12:49 [Qemu-devel] [PATCH v2 00/10] vnc-encodings Corentin Chary
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 01/10] vnc: refactor set_encodings Corentin Chary
2010-05-18 12:54 ` [Qemu-devel] " Alexander Graf
2010-05-18 18:09 ` Corentin Chary
2010-05-18 18:18 ` Alexander Graf
2010-05-18 19:23 ` Corentin Chary
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 02/10] vnc: really call zlib if we want zlib Corentin Chary
2010-05-18 12:54 ` [Qemu-devel] " Alexander Graf
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 03/10] vnc: only use a single zlib stream Corentin Chary
2010-05-18 12:51 ` [Qemu-devel] " Alexander Graf
2010-05-18 13:39 ` Anthony Liguori
2010-05-18 13:52 ` Alexander Graf
2010-05-18 13:55 ` Anthony Liguori
2010-05-18 13:56 ` Alexander Graf
2010-05-18 13:58 ` Anthony Liguori
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 04/10] vnc: adjust compression zstream level Corentin Chary
2010-05-18 12:55 ` [Qemu-devel] " Alexander Graf
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 05/10] vnc: add basic tight support Corentin Chary
2010-05-18 13:33 ` [Qemu-devel] " Anthony Liguori
2010-05-18 13:49 ` Alexander Graf
2010-05-18 13:54 ` Anthony Liguori
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 06/10] vnc: add support for tight fill encoding Corentin Chary
2010-05-18 13:34 ` [Qemu-devel] " Anthony Liguori
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 07/10] vnc: don't clear zlib stream on set_encoding Corentin Chary
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 08/10] vnc: remove memory leaks in zlib and tight encoding Corentin Chary
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 09/10] vnc: tight: add palette encoding Corentin Chary
2010-05-18 12:49 ` [Qemu-devel] [PATCH v2 10/10] vnc: update copyrights for vnc-encoding-tight.c Corentin Chary
2010-05-18 13:37 ` [Qemu-devel] " Anthony Liguori
2010-05-18 13:47 ` Chris Krumme [this message]
2010-05-18 17:26 ` Blue Swirl
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=4BF29A83.8030903@windriver.com \
--to=chris.krumme@windriver.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).