linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Nicholas D Steeves <nsteeves@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/2] Remove misleading BCP 78 boilerplate
Date: Mon, 18 Sep 2017 16:40:05 +0200	[thread overview]
Message-ID: <20170918144005.GC29043@twin.jikos.cz> (raw)
In-Reply-To: <20170917235227.6452-3-nsteeves@gmail.com>

On Sun, Sep 17, 2017 at 07:52:27PM -0400, Nicholas D Steeves wrote:
> BCP 78 applies to RFC 6234, but sha224-256.c is Simplified BSD.
> 
> This causes the following lintian error when building on Debian and
> Debian derivatives:
> 
>     E: btrfs-progs source: license-problem-non-free-RFC-BCP78
>        tests/sha224-256.c
> 
> Please consult the following email from debian-legal@lists.debian.org
> for more information:
> 
> https://lists.debian.org/debian-legal/2017/08/msg00004.html

Thanks, this looks like I've copied too much from the RFC and was not
aware of the BCP license issues. I believe the copyright notice(s) past
the line mentioning the filename(s) should be enough to satisfy the
licensing requirements and also the debian license checker.

  reply	other threads:[~2017-09-18 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17 23:52 [PATCH 0/2] btrfs-progs: tests/sha* copyright clarity and compliance fixes Nicholas D Steeves
2017-09-17 23:52 ` [PATCH 1/2] Add required IETF Trust copyright Nicholas D Steeves
2017-09-17 23:52 ` [PATCH 2/2] Remove misleading BCP 78 boilerplate Nicholas D Steeves
2017-09-18 14:40   ` David Sterba [this message]
2017-09-28 14:12     ` Nicholas D Steeves

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=20170918144005.GC29043@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nsteeves@gmail.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).