From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Disapproval of revision b8e46b797b32111526a2116d020fdd9e1c079965
Date: Thu, 08 May 2008 15:25:50 +0200 [thread overview]
Message-ID: <fvuv0v$16v$1@ger.gmane.org> (raw)
In-Reply-To: <74d0deb30805080534v6be5f293xa14fe5c159968555@mail.gmail.com>
pHilipp Zabel wrote:
> On Thu, May 8, 2008 at 1:21 PM, Rolf Leggewie
> <no2spam@nospam.arcornews.de> wrote:
>> Koen,
>>
>> thank you for continuing to keep such a close watch on every single
>> commit I make and raising hell every time you find a chance.
>
> Actually, I was just about to do the same thing (reverting, sending a
> notification, wouldn't call that raising hell) when I noticed Koen's
> disapproval, so thanks for the quick fix.
> Just saying, this is because gmp is a pretty prominent package, not
> because Koen is closely watching your every step. Of course the latter
> part is only an assumption.
I've been (trying) to build x11-image from scratch for various targets
the past week and fix any breakages I encounter. If you check the commit
messages you'll see that I'm also raising hell for the breakage Mickeyl
was so kind to add (removing packages that angstrom has as
PREFERRED_VERSION, etc).
It's nothing personal, Rolf just happened to be the person that made the
same mistake twice in a week.
FWIW: bitbake -c patch is IO limited, no cpu limited.
prev parent reply other threads:[~2008-05-08 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 6:58 Disapproval of revision b8e46b797b32111526a2116d020fdd9e1c079965 Koen Kooi
2008-05-08 11:21 ` Rolf Leggewie
2008-05-08 12:34 ` pHilipp Zabel
2008-05-08 13:25 ` Koen Kooi [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='fvuv0v$16v$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.