Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev strace: bump pr after last patch
Date: Sun, 15 Oct 2006 10:37:42 +1000	[thread overview]
Message-ID: <20061015003742.GB12679@twibble.org> (raw)
In-Reply-To: <E1GYf1g-00024R-9w@linuxtogo.org>

On Sat, Oct 14, 2006 at 10:37:48AM +0200, "koen commit" wrote:
> strace: bump pr after last patch

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...

-- 
 Jamie Lenehan <lenehan@twibble.org>



       reply	other threads:[~2006-10-15  0:44 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 ` Jamie Lenehan [this message]
2006-10-15  8:12   ` [oe-commits] org.oe.dev strace: bump pr after last patch Koen Kooi
2006-10-15 23:16     ` Jamie Lenehan

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=20061015003742.GB12679@twibble.org \
    --to=lenehan@twibble.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox