From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE][PATCH] opkg*: bump to r215 to fix segfaults on upgrade
Date: Mon, 13 Jul 2009 07:58:38 -0400 [thread overview]
Message-ID: <4A5B216E.6050105@balister.org> (raw)
In-Reply-To: <h3f65f$f0j$2@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Acked-by: Philip Balister <philip@balister.org>
Koen Kooi wrote:
> On 10-07-09 08:24, Koen Kooi wrote:
>> From: Koen Kooi<koen@openembedded.org>
>
> ping
>
>>
>>
>> Signed-off-by: Koen Kooi<koen@openembedded.org>
>> ---
>> conf/distro/include/sane-srcrevs.inc | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/conf/distro/include/sane-srcrevs.inc
>> b/conf/distro/include/sane-srcrevs.inc
>> index 6369462..7116c22 100644
>> --- a/conf/distro/include/sane-srcrevs.inc
>> +++ b/conf/distro/include/sane-srcrevs.inc
>> @@ -185,9 +185,9 @@ SRCREV_pn-openmoko-toolchain-scripts ?= "4913"
>> SRCREV_pn-openmoko-worldclock2 ?= "3365"
>> SRCREV_pn-openocd ?= "517"
>> SRCREV_pn-openocd-native ?= "517"
>> -SRCREV_pn-opkg ?= "209"
>> -SRCREV_pn-opkg-native ?= "209"
>> -SRCREV_pn-opkg-sdk ?= "209"
>> +SRCREV_pn-opkg ?= "215"
>> +SRCREV_pn-opkg-native ?= "215"
>> +SRCREV_pn-opkg-sdk ?= "215"
>> SRCREV_pn-opkg-utils ?= "4578"
>> SRCREV_pn-opkg-utils-native ?= "4595"
>> SRCREV_pn-oprofileui ?= "173"
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-07-13 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 6:24 [STABLE][PATCH] opkg*: bump to r215 to fix segfaults on upgrade Koen Kooi
2009-07-13 11:35 ` Koen Kooi
2009-07-13 11:58 ` Philip Balister [this message]
2009-07-13 11:57 ` Marcin Juszkiewicz
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=4A5B216E.6050105@balister.org \
--to=philip@balister.org \
--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 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.