From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix binutils fetch failure
Date: Mon, 29 Aug 2011 13:58:23 +0100 [thread overview]
Message-ID: <1314622703.5939.287.camel@rex> (raw)
In-Reply-To: <cover.1314563914.git.paul.eggleton@linux.intel.com>
On Sun, 2011-08-28 at 21:39 +0100, Paul Eggleton wrote:
> The following changes since commit 81aa4bfbde871af1d569b64499c34a315bf6218e:
>
> classes/sanity: enhance the network connectivity test (2011-08-25 08:49:12 -0700)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/binutils-2211a
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/binutils-2211a
>
> Paul Eggleton (1):
> binutils: update to 2.21.1a
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-08-29 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 20:39 [PATCH 0/1] Fix binutils fetch failure Paul Eggleton
2011-08-28 20:39 ` [PATCH 1/1] binutils: update to 2.21.1a Paul Eggleton
2011-08-29 18:14 ` Kumar Gala
2011-08-29 18:32 ` Paul Eggleton
2011-08-29 12:58 ` Richard Purdie [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=1314622703.5939.287.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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