All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: "Dr. Michael Lauer" <mickey@vanille-media.de>
Cc: board@openembedded.org, openembedded-devel@lists.openembedded.org
Subject: Re: problems compiling glibc_2.9-r37.4 under Angstrom
Date: Mon, 24 Jan 2011 16:49:51 +0000	[thread overview]
Message-ID: <4D3DADAF.8000805@xora.org.uk> (raw)
In-Reply-To: <B3A1C536-8344-410C-A58F-F5378AC5AB12@vanille-media.de>

9-5 GMT weds-fri is normally ok with me, outisde these times I work a 
totally non related job.

G

On 24/01/2011 16:46, Dr. Michael Lauer wrote:
> ping?
>
> Am 21.01.2011 um 16:12 schrieb Dr. Michael Lauer:
>
>> Philip,
>>
>> unfortunately you're not commenting on Frans' actual point,
>> which no longer has anything to do with the u-boot thing.
>>
>> Board, when can we schedule a meeting?
>>
>> :M:
>>




  reply	other threads:[~2011-01-24 16:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 18:12 problems compiling glibc_2.9-r37.4 under Angstrom Víctor M. Jáquez L.
2011-01-20 21:40 ` Khem Raj
2011-01-21 10:21   ` Víctor M. Jáquez L.
2011-01-22 11:29     ` Frans Meulenbroeks
2011-01-21 11:03 ` Koen Kooi
2011-01-21 11:29   ` Frans Meulenbroeks
2011-01-21 11:34     ` Dr. Michael Lauer
2011-01-21 14:30     ` Philip Balister
2011-01-21 15:12       ` Dr. Michael Lauer
2011-01-24 16:46         ` Dr. Michael Lauer
2011-01-24 16:49           ` Graeme Gregory [this message]
2011-01-24 19:59             ` Board meeting, was: " Philip Balister
2011-01-22  0:29       ` Khem Raj
2011-01-22 12:10         ` Frans Meulenbroeks
2011-01-22  0:21   ` Khem Raj
2011-01-22 11:10     ` Koen Kooi
2011-01-22 12:36       ` Frans Meulenbroeks
2011-01-22 12:39         ` Frans Meulenbroeks
2011-01-22 15:28         ` Graeme Gregory
2011-01-22 16:30           ` Frans Meulenbroeks

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=4D3DADAF.8000805@xora.org.uk \
    --to=dp@xora.org.uk \
    --cc=board@openembedded.org \
    --cc=mickey@vanille-media.de \
    --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.