From: Jamie Lenehan <lenehan@twibble.org>
To: Koen Kooi <koen@dominion.kabel.utwente.nl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev strace: bump pr after last patch
Date: Mon, 16 Oct 2006 09:16:31 +1000 [thread overview]
Message-ID: <20061015231631.GA6215@twibble.org> (raw)
In-Reply-To: <4531ED53.1050506@dominion.kabel.utwente.nl>
On Sun, Oct 15, 2006 at 10:12:03AM +0200, Koen Kooi wrote:
[...]
> > Was there some reason for this? (Just to make sure I didn't miss
> > something!) In this case it had no effect on any existing strace
> > build (the change is a no-op for glibc < 2.5) and since glibc 2.5
> > didn't build previously it can't have had any change on glibc 2.5
> > built strace's...
>
> People who's build broke (like me :) ) wouldn't get past it because OE tries to finish
> building the unpatched version. I was trying to avoid the 'I updated and it still fails'
Ahh, yep... that is something I didn't think of. I'll keep that in
mind in the future.
Thanks!
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2006-10-15 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GYf1g-00024R-9w@linuxtogo.org>
2006-10-15 0:37 ` [oe-commits] org.oe.dev strace: bump pr after last patch Jamie Lenehan
2006-10-15 8:12 ` Koen Kooi
2006-10-15 23:16 ` Jamie Lenehan [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=20061015231631.GA6215@twibble.org \
--to=lenehan@twibble.org \
--cc=koen@dominion.kabel.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.