From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2][dizzy] python-nose and python-contextlib backports to dizzy
Date: Tue, 09 Jun 2015 17:19:49 -0500 [thread overview]
Message-ID: <55776685.6030109@linux.intel.com> (raw)
In-Reply-To: <14059572.S7Ebuh4W14@peggleto-mobl.ger.corp.intel.com>
Sorry about that, I actually made a mistake, and somehow got confused,
apparently python-nose is already in [dizzy], I'd still like to
backport python-contextlib, the original patch does not apply cleanly;
hence this one can be used
On 09/06/15 05:01, Paul Eggleton wrote:
> Alejandro / Armin
>
> When we backport things, ideally we should be backporting the patch that
> originally added them (assuming it was a single patch). Otherwise we definitely
> want some kind of context in the commit message.
>
> Alejandro, since we're backporting to dizzy, can you also confirm none of these
> patches are needed for fido? It looks like they aren't, but I can't be sure.
>
> Cheers,
> Paul
>
> On Monday 08 June 2015 17:37:06 akuster808 wrote:
>> Alejandro,
>>
>> great. I pull these in.
>>
>>
>> thanks,
>> - armin
>>
>> On 06/08/2015 06:56 AM, Alejandro Hernandez wrote:
>>> I would like to backport both python-nose and python-contextlib to dizzy,
>>> they were added to master in the following commits respectively:
>>>
>>>
>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7282635343e0ccf7
>>> a82ffdb35905bdc2db6093d3
>>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7f58a85337a0712
>>> 802bdb604a58985a8800b6477
>>>
>>> I would like to include python-scipy, and these are build dependencies for
>>> it, more specifically for iot builds which currently use the dizzy branch>
>>> The following changes since commit
> 9c4ff467f66428488b1cd9798066a8cb5d6b4c3b:
>>> split_and_strip_files: regroup hardlinks to make build deterministic
>>> (2015-05-15 18:13:40 +0100)>
>>> are available in the git repository at:
>>> git://git.yoctoproject.org/poky-contrib hsalejandro/iot_backports
>>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=hsalejandro/io
>>> t_backports>
>>> Alejandro Hernandez (2):
>>> python-contextlib: backport to dizzy
>>> python-nose: backport it to dizzy
>>>
>>> meta/recipes-devtools/python/python-2.7-manifest.inc | 10 +++++++---
>>> meta/recipes-devtools/python/python-nose_1.3.6.bb | 16
>>> ++++++++++++++++
>>> scripts/contrib/python/generate-manifest-2.7.py | 3 +++
>>> 3 files changed, 26 insertions(+), 3 deletions(-)
>>> create mode 100644 meta/recipes-devtools/python/python-nose_1.3.6.bb
prev parent reply other threads:[~2015-06-09 22:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 13:56 [PATCH 0/2][dizzy] python-nose and python-contextlib backports to dizzy Alejandro Hernandez
2015-06-08 13:56 ` [PATCH 1/2][dizzy] python-contextlib: backport " Alejandro Hernandez
2015-06-14 5:52 ` akuster808
2015-06-08 13:56 ` [PATCH 2/2][dizzy] python-nose: backport it " Alejandro Hernandez
2015-06-14 5:56 ` akuster808
2015-06-14 16:13 ` Khem Raj
2015-06-14 23:12 ` akuster808
2015-06-15 11:42 ` Otavio Salvador
2015-06-09 0:37 ` [PATCH 0/2][dizzy] python-nose and python-contextlib backports " akuster808
2015-06-09 10:01 ` Paul Eggleton
2015-06-09 22:19 ` Alejandro Hernandez [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=55776685.6030109@linux.intel.com \
--to=alejandro.hernandez@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox