Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dropbear: add license information
Date: Wed, 12 Sep 2012 18:12:42 +0200	[thread overview]
Message-ID: <5050B47A.10504@mind.be> (raw)
In-Reply-To: <50503FB3.6080807@mimc.co.uk>

On 09/12/12 09:54, Mark Jackson wrote:
> Signed-off-by: Mark Jackson<mpfj@newflow.co.uk>
> ---
>   package/dropbear/dropbear.mk |    2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/package/dropbear/dropbear.mk b/package/dropbear/dropbear.mk
> index 64d3a01..cd349b0 100644
> --- a/package/dropbear/dropbear.mk
> +++ b/package/dropbear/dropbear.mk
> @@ -6,6 +6,8 @@
>
>   DROPBEAR_VERSION = 2012.55
>   DROPBEAR_SITE = http://matt.ucc.asn.au/dropbear/releases
> +DROPBEAR_LICENSE = dropbear license
> +DROPBEAR_LICENSE_FILES = LICENSE

  I'd call it "MIT BSD-2c public domain", that's more descriptive.

  Luca and others: what should we do when several licenses apply?
Up to now, we've always just put a space between them, but the problem
is that something like "public domain" already has a space. Maybe it's
better to put

MIT && BSD-2c && public domain

?

Regards,
Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2012-09-12 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  7:54 [Buildroot] [PATCH] dropbear: add license information Mark Jackson
2012-09-12 16:12 ` Arnout Vandecappelle [this message]

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=5050B47A.10504@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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