Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC/PATCH] Perl 5.10.1 and a bunch of modules
Date: Fri, 19 Mar 2010 23:47:16 +0100	[thread overview]
Message-ID: <ho0utk$tqs$1@dough.gmane.org> (raw)
In-Reply-To: <20100319211220.GI2425@xora-desktop.xora.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19-03-10 22:12, Graeme Gregory wrote:
> On Sat, Mar 20, 2010 at 12:05:35AM +0300, Roman I Khimov wrote:
>> В сообщении от Пятница 19 марта 2010 00:23:25 автор Roman I Khimov написал:
>>> В сообщении от Пятница 19 марта 2010 00:04:30 автор Roman I Khimov написал:
>>>> В сообщении от Четверг 18 марта 2010 23:47:01 автор Roman I Khimov 
>> написал:
>>>>> No. You mean, this one?
>>>>> http://git.pokylinux.org/cgit.cgi/poky/commit/?id=ca5f36ee6ad756e1e5402
>>>>> 88 a5 6a504c1d8ecc7a3
>>>>>
>>>>> Looks like a good thing to have, so if Richard will push it to OE.dev I
>>>>> can do a rebase of my patchset.
>>>>
>>>> Actually, the better sequence is
>>>>  * drop 5.8.4 and 5.8.7
>>>>  * bring in staging changes
>>>>  * bring in 5.10.1
>>>>
>>>> I'll prepare 5.8.4/5.8.7 removal patch.
>>>
>>> Updated rik/perl-5.10 branch with removal patch, please ACK.
>>
>> Tried to compile for arm, succeeded with perl, discovered and fixed some 
>> problems in modules. Updated the branch.
>>
>> I think I need some ACK's for dusty old Perl versions removal and then 
>> Richard's Perl staging update could be merged better on top of that (CC'ing 
>> Richard) and than I'll update 5.10.1 to new staging and push the series. At 
>> least, that's how I think it should be. If there are any problems with staging 
>> update and it's not ready to be pushed in OE.dev, I think we can merge 5.10.1 
>> as it is now.
>>
> For removal of old perl versions
> 
> Acked-by: Graeme Gregory <dp@xora.org.uk>

Acked-by: Koen Kooi <koen@openembedded.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLo/70MkyGM64RGpERAixEAJwJOkgBATjeiofMEyyZGpH4WhMk8ACeMn2t
4wFDmIwNNd1tgnO0Syx94dE=
=Vzni
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-03-19 22:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18 19:12 [RFC/PATCH] Perl 5.10.1 and a bunch of modules Roman I Khimov
2010-03-18 19:36 ` Frans Meulenbroeks
2010-03-18 19:46   ` Roman I Khimov
2010-03-18 19:50 ` Roman I Khimov
2010-03-18 20:30 ` Koen Kooi
2010-03-18 20:47   ` Roman I Khimov
2010-03-18 21:04     ` Roman I Khimov
2010-03-18 21:23       ` Roman I Khimov
2010-03-19 21:05         ` Roman I Khimov
2010-03-19 21:12           ` Graeme Gregory
2010-03-19 22:47             ` Koen Kooi [this message]
2010-03-20  8:49             ` Frans Meulenbroeks
2010-03-23 13:51           ` Roman I Khimov
2010-03-20 14:49 ` Koen Kooi
2010-03-21 12:05   ` Roman I Khimov
2010-03-23 21:51     ` [PATCH 01/44] cpan-base: add perl version to PR Roman I Khimov
2010-03-24 12:57       ` Roman I Khimov
2010-03-24 16:09         ` Koen Kooi
2010-03-24 17:26           ` Roman I Khimov
2010-03-24 17:41             ` Marcin Juszkiewicz
2010-03-24 17:55               ` Roman I Khimov
2010-03-25  7:28                 ` Koen Kooi
2010-03-25  7:35                   ` Roman I Khimov
2010-03-24 17:58               ` Roman I Khimov

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='ho0utk$tqs$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /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