From: Martin Jansa <martin.jansa@gmail.com>
To: "S. Lockwood-Childs" <sjl@vctlabs.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCHv3 3/3] python-tornado: add missing python2 runtime deps
Date: Thu, 2 Jun 2016 21:43:13 +0200 [thread overview]
Message-ID: <20160602194313.GC2571@jama> (raw)
In-Reply-To: <20160602185856.GA7939@vctlabs.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Thu, Jun 02, 2016 at 11:58:56AM -0700, S. Lockwood-Childs wrote:
> On Thu, Jun 02, 2016 at 11:28:01AM -0700, S. Lockwood-Childs wrote:
> > +RDEPENDS_${PN} += "${PYTHON_PN}-backports-ssl ${PYTHON_P}-backports-abc ${PYTHON_PN}-singledispatch"
>
> Well that's really fun -- I managed to pick the version of the patch with the
> typo when splitting it up. Do I have to send the whole series again to add one
> letter (PYTHON_P -> PYTHON_PN) ?
I'll try not to forget to change it when cherry-picking to master-next.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2016-06-02 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 18:24 [meta-python][PATCHv3 0/3] Tornado 4.3 is missing python2 RDEPENDS S. Lockwood-Childs
2016-06-02 18:26 ` [meta-python][PATCHv3 1/3] python-backports-abc: initial recipe for version 0.4 RDEPENDS S. Lockwood-Childs
2016-06-03 5:03 ` Gary Thomas
2016-06-03 5:38 ` S. Lockwood-Childs
2016-06-03 5:47 ` Gary Thomas
2016-06-03 5:55 ` S. Lockwood-Childs
2016-06-02 18:27 ` [meta-python][PATCHv3 2/3] python-singledispatch: initial recipe for version 3.4.0.3 S. Lockwood-Childs
2016-06-02 18:28 ` [meta-python][PATCHv3 3/3] python-tornado: add missing python2 runtime deps S. Lockwood-Childs
2016-06-02 18:58 ` S. Lockwood-Childs
2016-06-02 19:43 ` Martin Jansa [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=20160602194313.GC2571@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sjl@vctlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.