qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit
Date: Mon, 7 Mar 2016 14:10:46 -0700	[thread overview]
Message-ID: <56DDEE56.60002@redhat.com> (raw)
In-Reply-To: <B97D45A0-AC73-4C02-93AC-D09E7280021D@gmail.com>

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

On 03/06/2016 01:35 PM, Programmingkid wrote:
> 
> On Mar 5, 2016, at 7:02 PM, Eric Blake wrote:
> 
>> On 03/04/2016 10:15 PM, Programmingkid wrote:
>>>
>>
>>> + *
>>> + * Permission is hereby granted, free of charge, to any person obtaining a copy
>>> + * of this software and associated documentation files (the "Software"), to deal
>>> + * in the Software without restriction, including without limitation the rights
>>> + * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
>>> + * copies of the Software, and to permit persons to whom the Software is
>>> + * furnished to do so, subject to the following conditions:
>>
>> Any reason you chose the weaker BSD license instead of the
>> project-default of GPLv2+?
> 
> Could you provide a file name or a link that has the exact text you wish to see in the file?

BSD is just fine, if you have a strong reason for preferring it (it is a
weaker license than GPLv2+, which means GPL code can import BSD code,
but BSD code can't import GPL code.  Personally, I try to avoid the BSD
license on my code, because I don't like the fact that it allows
companies to make a proprietary fork of my code, while the GPL
guarantees that anyone using my code will keep it free.  But other
people don't like the GPL and intentionally favor BSD for things they
write for maximum uptake of their code.)

If you don't have a strong license preference, then there are plenty of
GPLv2+ files you can copy from:

$ git grep -l 'GPL, version 2 or' | wc -l
482

> 
>> Can you provide a URL to the source document that you used for coming up
>> with this list, so that we can better double-check your work?  (Do it as
>> a comment in this file, if you have one)
> 
> Does this look good:
> 
> /*
>  *  adb-keys.h
>  *
>  *  Provides an enum of all the Macintosh keycodes.
>  *  Note: keys like Power, volume related, and eject are handled at a lower
>  *        level and are not available to QEMU. That doesn't mean we can't
>  *        substitute one key for another. The function keys like F1 make a good
>  *        substitute for these keys. This can be done in the GTK, SDL, or Cocoa
>  *        code.
>  *  Additional information: http://stackoverflow.com/questions/3202629/where-can
>  *                          -i-find-a-list-of-mac-virtual-key-codes

The URL is line-broken; but still works (since stackoverflow only cares
about the 3202629/ prefix). But yes, that sort of information source is
useful as a code comment.

-- 
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: 604 bytes --]

  reply	other threads:[~2016-03-07 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05  5:15 [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit Programmingkid
2016-03-06  0:02 ` Eric Blake
2016-03-06  0:06   ` Programmingkid
2016-03-06 20:35   ` Programmingkid
2016-03-07 21:10     ` Eric Blake [this message]
2016-03-07 21:33       ` Programmingkid
2016-03-07 21:44         ` 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=56DDEE56.60002@redhat.com \
    --to=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.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).