From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Michael Halstead <michael@yoctoproject.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Best way to update gnu-config?
Date: Wed, 03 Oct 2012 18:25:51 +0100 [thread overview]
Message-ID: <506C751F.50702@linaro.org> (raw)
In-Reply-To: <506C74C7.7090006@yoctoproject.org>
W dniu 03.10.2012 18:24, Michael Halstead pisze:
> On 10/03/2012 07:51 AM, Marcin Juszkiewicz wrote:
>> W dniu 18.09.2012 11:36, Richard Purdie pisze:
>>> Thanks, Michael should be able to take care of this later today (he's US
>>> based).
>>
>> Michael: any update on it?
>>
> I'm sorry this is a case of bad e-mail filtering.
>
> I've added this tarball at
> http://downloads.yoctoproject.org/releases/gnu-config/ is that correct?
Thanks a lot - that was it.
next prev parent reply other threads:[~2012-10-03 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 8:58 Best way to update gnu-config? Marcin Juszkiewicz
2012-09-18 9:00 ` [PATCH 1/2] ncurses: Update gnu-config files to version used by OE-Core Marcin Juszkiewicz
2012-09-18 9:00 ` [PATCH 2/2] db: " Marcin Juszkiewicz
2012-09-18 11:20 ` Burton, Ross
2012-09-18 11:43 ` Marcin Juszkiewicz
2012-09-18 10:40 ` [PATCH 1/2] ncurses: " Koen Kooi
2012-09-18 10:43 ` Marcin Juszkiewicz
2012-10-08 16:32 ` [PATCH 1/4] autotools.bbclass: update gnu-config files always Marcin Juszkiewicz
2012-10-09 4:38 ` Chris Larson
2012-10-09 20:01 ` [PATCH] " Marcin Juszkiewicz
2012-10-09 22:34 ` Richard Purdie
2012-10-10 10:55 ` Marcin Juszkiewicz
2012-09-18 9:08 ` Best way to update gnu-config? Richard Purdie
2012-09-18 9:29 ` Marcin Juszkiewicz
2012-09-18 10:36 ` Richard Purdie
2012-10-03 14:51 ` Marcin Juszkiewicz
2012-10-03 17:24 ` Michael Halstead
2012-10-03 17:25 ` Marcin Juszkiewicz [this message]
2012-10-08 16:24 ` [PATCH] gnu-config: update to 2012.08.14 to get support for AArch64 architecture Marcin Juszkiewicz
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=506C751F.50702@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=michael@yoctoproject.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