Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] python-argh: new package
Date: Tue, 31 May 2016 21:16:34 +0200	[thread overview]
Message-ID: <20160531211634.52b7169e@free-electrons.com> (raw)
In-Reply-To: <1462515686-26545-1-git-send-email-yegorslists@googlemail.com>

Hello,

On Fri,  6 May 2016 08:21:24 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  package/Config.in                    |  1 +
>  package/python-argh/Config.in        |  6 ++++++
>  package/python-argh/python-argh.hash |  4 ++++
>  package/python-argh/python-argh.mk   | 13 +++++++++++++
>  4 files changed, 24 insertions(+)
>  create mode 100644 package/python-argh/Config.in
>  create mode 100644 package/python-argh/python-argh.hash
>  create mode 100644 package/python-argh/python-argh.mk

I've added PYTHON_ARGH_LICENSE_FILES, pointing to README.rst, which
contains a reference to the license. Not perfect, but better than
nothing.

Applied to next with this change.

THanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2016-05-31 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06  6:21 [Buildroot] [PATCH 1/3] python-argh: new package yegorslists at googlemail.com
2016-05-06  6:21 ` [Buildroot] [PATCH 2/3] python-pathtools: " yegorslists at googlemail.com
2016-05-31 19:19   ` Thomas Petazzoni
2016-05-06  6:21 ` [Buildroot] [PATCH 3/3] python-watchdog: " yegorslists at googlemail.com
2016-05-31 19:19   ` Thomas Petazzoni
2016-05-31 19:16 ` 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=20160531211634.52b7169e@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