From: Karel Zak <kzak@redhat.com>
To: Carlos Santos <casantos@datacom.ind.br>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] docs: add ISC licence
Date: Wed, 17 Jan 2018 14:39:44 +0100 [thread overview]
Message-ID: <20180117133944.wltrmm2ixo32ctoo@ws.net.home> (raw)
In-Reply-To: <20180114183931.10494-1-casantos@datacom.ind.br>
On Sun, Jan 14, 2018 at 04:39:31PM -0200, Carlos Santos wrote:
> Save the top 21 lines of sys-utils/rfkill.c as COPYING.ISC. This is
> useful for Linux distributions an integration tools like Buildroot,
> to collect detailed legal information for each package.
>
> Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
> ---
> Documentation/licenses/COPYING.ISC | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/licenses/COPYING.ISC
Applied (without C-comments and rfkill stuff), thanks.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2018-01-17 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 18:39 [PATCH] docs: add ISC licence Carlos Santos
2018-01-17 13:39 ` Karel Zak [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=20180117133944.wltrmm2ixo32ctoo@ws.net.home \
--to=kzak@redhat.com \
--cc=casantos@datacom.ind.br \
--cc=util-linux@vger.kernel.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).