From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs
Date: Wed, 17 Feb 2010 22:22:39 +0100 [thread overview]
Message-ID: <hlhmn0$5c2$1@ger.gmane.org> (raw)
In-Reply-To: <1266437931.5691.30.camel@trini-m4400>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17-02-10 21:18, Tom Rini wrote:
> On Wed, 2010-02-17 at 08:59 +0000, git version control wrote:
>> Module: openembedded.git
>> Branch: org.openembedded.dev
>> Commit: 74501117c261f743c76ae3c2988cbcfdc141cf3a
>> URL: http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=74501117c261f743c76ae3c2988cbcfdc141cf3a
>>
>> Author: Koen Kooi <koen@openembedded.org>
>> Date: Tue Feb 16 13:08:53 2010 +0100
>>
>> opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs
>
> I'd like to RFC that we do something like:
> OPKGREV ?= "522"
> SRCREV_pn-opkg ?= "${OPKGREV}"
> SRCREV_pn-opkg-native ?= "${OPKGREV}"
> SRCREV_pn-opkg-sdk ?= "${OPKGREV}"
>
> And if -nogpg or what have you is broken, it either gets fixed or the
> distribution takes advantage of that ?=.
I haven't been able to properly test a target opkg yet, so no bump for
that. Unless people would like broken opkg binaries on their target ;)
Personally, I want sanesrcrev.inc to die and put the revs in the recipes
where they belong.
> It seems a bit silly,
> especially given the nature of the fixes, to split things up like this.
> Heck, assuming 521 -> 522 is the patch from RP, the original report was
> for on target opkg, not do_rootfs
The commit does what is says in the message, it removes duplicate
entries in do_rootfs logs (and makes narciusses XHR smaller), so what is
it you're complaining about?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLfF4fMkyGM64RGpERAtzxAJ4pekG+XqhcG2datLFAtmtRv8qWuwCfWxqh
NViFLd7Oq2iEyAQdE3/C+8c=
=Glgp
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-02-17 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Nhfko-0005KL-8Z@melo.openembedded.org>
2010-02-17 20:18 ` [oe-commits] Koen Kooi : opkg-native: bump to r522 to get a fix to remove duplicate messages from do_rootfs logs Tom Rini
2010-02-17 21:22 ` Koen Kooi [this message]
2010-02-17 21:43 ` Tom Rini
2010-02-18 9:09 ` Koen Kooi
2010-02-18 22:50 ` Graham Gower
2010-02-23 12:10 ` Florian Boor
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='hlhmn0$5c2$1@ger.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 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.