Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Peter Leemans <peter@bist2.be>
To: openembedded-devel@lists.openembedded.org
Subject: Re: FOSDEM'07
Date: Thu, 16 Nov 2006 18:24:07 +0100	[thread overview]
Message-ID: <1163697847.6223.25.camel@localhost.localdomain> (raw)
In-Reply-To: <c384c5ea0611160830s1ca8f393o2e41b427c80c4f06@mail.gmail.com>



On Thu, 2006-11-16 at 17:30 +0100, Leon Woestenberg wrote:
> On 11/16/06, Michael 'Mickey' Lauer
> <mickey@tm.informatik.uni-frankfurt.de> wrote:
> > I want to have three people at the stand during the day, but at the same
> > time being able for everyone to have enough time wandering around @
> >

> > Who else would like to be there and present OE?
> >
> I do not consider myself a OE developer in the same league as yours
> truly and consortium, but if you need people at the booth you can hire
> m... ehh... count me in as a volunteer. Otherwise, I will probably be
> hanging out on the frontside of the booth anyway.

Hi All,

If I can be of any use, I'll be glad to help.
I'll be at fosdem anyway, so better make myself usefull.

Regards,
Peter Leemans





  parent reply	other threads:[~2006-11-16 17:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-16 16:11 FOSDEM'07 Michael 'Mickey' Lauer
2006-11-16 16:30 ` FOSDEM'07 Leon Woestenberg
2006-11-16 17:21   ` FOSDEM'07 Richard Purdie
2006-11-16 17:24   ` Peter Leemans [this message]
2006-11-17 15:28 ` FOSDEM'07 Marcin Juszkiewicz
2006-11-17 15:33   ` FOSDEM'07 Koen Kooi
2006-11-26 21:22     ` FOSDEM'07 Marcin Juszkiewicz
2006-11-26 21:32       ` FOSDEM'07 Michael 'Mickey' Lauer
2006-11-26 21:41         ` FOSDEM'07 Richard Purdie
2006-11-26 22:21           ` FOSDEM'07 Michael 'Mickey' Lauer
2006-11-27  0:24             ` FOSDEM'07 Richard Purdie
2006-11-27 10:10             ` FOSDEM'07 Richard Purdie
2006-11-27 10:20               ` FOSDEM'07 Koen Kooi
2006-11-27 11:46                 ` FOSDEM'07 Michael 'Mickey' Lauer
2006-11-30 13:37   ` FOSDEM'07 Stelios Koroneos
2006-12-06 13:43     ` FOSDEM'07 Stelios Koroneos
2006-12-07 17:02       ` FOSDEM'07 Leon Woestenberg
2006-12-07 17:36         ` FOSDEM'07 Michael 'Mickey' Lauer
2006-12-07 19:04           ` FOSDEM'07 Leon Woestenberg
2006-12-07 19:34             ` FOSDEM'07 Michael 'Mickey' Lauer
2006-12-07 22:53             ` FOSDEM'07 Richard Purdie
2006-12-07 23:45               ` FOSDEM'07 Michael 'Mickey' Lauer
2006-12-08 22:36                 ` FOSDEM'07 Leon Woestenberg
2006-12-08 23:01                 ` FOSDEM'07 Leon Woestenberg
2006-12-08 22:10               ` FOSDEM'07 Leon Woestenberg
2006-12-08 22:11                 ` FOSDEM'07 Leon Woestenberg
2006-12-09 10:39                   ` FOSDEM'07 Bastian Ballmann
2006-12-11 18:46                     ` FOSDEM'07 Tim Bird
2006-12-11 22:43                       ` FOSDEM'07 Michael 'Mickey' Lauer
2006-12-11 23:46                         ` FOSDEM'07 Tim Bird
2006-12-11 23:50                           ` FOSDEM'07 Michael 'Mickey' Lauer
2006-12-12  8:40                             ` FOSDEM'07 Stelios Koroneos
2006-12-11 23:53                           ` FOSDEM'07 Michael 'Mickey' Lauer

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=1163697847.6223.25.camel@localhost.localdomain \
    --to=peter@bist2.be \
    --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