From: akuster808 <akuster808@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [meta-python][krogoth] Backport python recipes
Date: Mon, 25 Apr 2016 11:24:49 -0700 [thread overview]
Message-ID: <571E60F1.2020804@gmail.com> (raw)
In-Reply-To: <CAP9ODKrfCC+Nyr9EHd931gnoVsyngZ1hvBfBwT4izx4TiOf-Zg@mail.gmail.com>
On 04/25/2016 11:06 AM, Otavio Salvador wrote:
> Armin,
>
> On Mon, Apr 25, 2016 at 10:45 AM, Fabio Berton
> <fabio.berton@ossystems.com.br> wrote:
>> Hi all,
>>
>> Recently I sent some python recipes for review and last week were merged to
>> master. Could these recipes be backported for krogoth? I tested all them in
>> krogoth branch.
>>
>> Recipes are listed bellow:
>>
>> python-bcrypt: cb95c5edaa977c8361628dab04b95192c423fc1a
>> python-blinker: 5a7f267941689eff28b4b0721752708bad4747b6
>> python-flask-bcrypt: 00d5837fd39af7ffae262282f56a0cb42a1c3b89
>> python-flask-bootstrap: 962e2ab371844f5119df2b8ab4a4231f6f7f9f3d
>> python-flask-navigation: 381d498441bd66bdae2d8da1ddcaadee1ff6de73
>> python-flask-sqlalchemy: 3e4ecdd6fe6709f394d92e86ccbc228ae5a43663
>> python-flask-wtf: 4be70064670c34d1b67224672b7caed7b4ed7b04
>> python-pam: 49b35175d5018dc626a17a9a0662d97e812aab7c
>> python-wtforms: 9676ebb7d14090126f667671d525ce3f3ee89279
>> python-dominate: 5a20e8799eb1c1dd38ec9fee15fd90b88b38bba4
>> python-netaddr: d3767d923d5044604633be3a3ba8bb4564f51b04
>> python-visitor: 834392bfada652260f6d5924278dd5839d095941
>
> Please check above. To be honest, I think all in meta-oe master could
> go to krogoth but you are the one to decide on this.
>
its on my list to check.
regards,
- armin
next prev parent reply other threads:[~2016-04-25 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 13:45 [meta-python][krogoth] Backport python recipes Fabio Berton
2016-04-25 18:06 ` Otavio Salvador
2016-04-25 18:24 ` akuster808 [this message]
2016-05-01 16:17 ` akuster808
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=571E60F1.2020804@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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