From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/alsamixergui: add license information
Date: Fri, 3 Mar 2017 08:35:54 +0100 [thread overview]
Message-ID: <20170303083554.344bb5cc@free-electrons.com> (raw)
In-Reply-To: <500f6a12-4b0d-b979-83d6-348bc6bd5b9d@grandegger.com>
Hello,
On Fri, 3 Mar 2017 08:34:58 +0100, Wolfgang Grandegger wrote:
> OK! How should I/we fix that problem? With a patch adding the COPYING
> file or we simply don't provide ALSAMIXERGUI_LICENSE_FILES.
As I suggested in my previous reply: use debian/copyright.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-03 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 16:06 [Buildroot] [PATCH] package/alsamixergui: add license information Wolfgang Grandegger
2017-03-02 16:16 ` Thomas Petazzoni
[not found] ` <c6240c78-d0ee-a3c8-681a-b041f963f72c@grandegger.com>
2017-03-02 20:37 ` Thomas Petazzoni
2017-03-03 7:34 ` Wolfgang Grandegger
2017-03-03 7:35 ` Thomas Petazzoni [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=20170303083554.344bb5cc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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