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] python-hyperlink: new package
Date: Wed, 12 Jul 2017 18:38:21 +0200	[thread overview]
Message-ID: <20170712183821.5a4245be@windsurf.lan> (raw)
In-Reply-To: <20170712075743.15082-1-yegorslists@googlemail.com>

Hello,

On Wed, 12 Jul 2017 09:57:43 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
> 
> Though PyPI says the license is BSD, GitHub repo has an MIT license
> file since April 2017 and upstream setup.py was also fixed.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  package/Config.in                              |  1 +
>  package/python-hyperlink/Config.in             |  6 ++++++
>  package/python-hyperlink/python-hyperlink.hash |  3 +++
>  package/python-hyperlink/python-hyperlink.mk   | 13 +++++++++++++
>  4 files changed, 23 insertions(+)
>  create mode 100644 package/python-hyperlink/Config.in
>  create mode 100644 package/python-hyperlink/python-hyperlink.hash
>  create mode 100644 package/python-hyperlink/python-hyperlink.mk

Applied to master, thanks. However, when you send individual patches,
make sure they applied on master. Indeed in this patch, the context
in package/Config.in referred to the python-hyperframe package, which
you submitted in a different patch series, that hasn't been merged yet.
This caused a conflict (admittedly minor and very easy to resolve) when
applying the patch.

Best regards,

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

      reply	other threads:[~2017-07-12 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  7:57 [Buildroot] [PATCH] python-hyperlink: new package yegorslists at googlemail.com
2017-07-12 16:38 ` 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=20170712183821.5a4245be@windsurf.lan \
    --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