From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] update opkg* SRCREV to 201
Date: Thu, 26 Feb 2009 10:46:00 -0500 [thread overview]
Message-ID: <49A6B938.3040201@balister.org> (raw)
In-Reply-To: <go6ah4$cud$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Koen Kooi wrote:
> On 25-02-09 21:46, Koen Kooi wrote:
>> Hi,
>>
>> I was getting seriously annoyed with the useless error codes opkg was
>> giving me and Tick pointed me to:
>>
>> http://code.google.com/p/opkg/issues/detail?id=6&can=1
>>
>> We're at 197 now in OE (with r201 applied as patch). I'd like to get
>> r199 and r200 in as well, and since I'm lazy I though we'd get r198 in
>> as well, which means instead of adding a few patches I can just bump up
>> SRCREV to 201.
>>
>> What do you think?
>
> Noone is thinking anything?
Well, it looks ok to me, but I am not a follower of opkg.
Hearing no positive comments, does anyone object to pushing this,
knowing that if Koen is wrong about this working, it messes up our builds?
Philip
[*] Yes, that is an awful sentence.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-02-26 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:46 [RFC] update opkg* SRCREV to 201 Koen Kooi
2009-02-26 14:55 ` Koen Kooi
2009-02-26 15:40 ` Tom Rini
2009-02-27 7:20 ` Koen Kooi
2009-02-27 19:56 ` Tom Rini
2009-02-26 15:46 ` Philip Balister [this message]
2009-02-26 19:09 ` Mike (mwester)
2009-02-26 16:13 ` Graeme Gregory
2009-02-26 18:31 ` Tick
2009-02-26 19:41 ` Michael 'Mickey' Lauer
2009-02-26 20:25 ` Mike (mwester)
2009-02-27 19:31 ` Koen Kooi
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=49A6B938.3040201@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.