Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tobias Pflug <tobias.pflug@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: hello...
Date: Thu, 04 Oct 2007 12:41:27 +0200	[thread overview]
Message-ID: <1191494488.2516.34.camel@toontown> (raw)

hey..

I just wanted to say hi to everyone on this list. I recently started
working with OpenEmbedded. I'm using it at work for an embedded solution
using the compulab boards. So far I am mostly enjoying the "openembedded
experience"..

The documenation could be a bit better and less scattered over different
places but well.. noone loves writing documentation. But I have received
good and friendly support from the #oe irc channel.

The next point will perhaps not make me many friends on this list, but
I am not exactly too fond of monotone. I for one would prefer if
openembedded used git. Mostly because it is *so* much faster. My machine
is fairly decent I would say and still the usage experience isn't that
great. (`mtn status` = zZzz :)

anyway, I look forward to using OE more and hopefully also contributing
to it.

best regards,
Tobi




             reply	other threads:[~2007-10-04 10:46 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-04 10:41 Tobias Pflug [this message]
2007-10-04 11:18 ` hello Michael Krelin
2007-10-04 12:40   ` hello Holger Freyther
2007-10-04 12:55     ` monotone/git (was hello...) Tobias Pflug
2007-10-04 13:27       ` Holger Freyther
2007-10-04 13:50         ` Darcy Watkins
2007-10-04 13:52           ` Michael Krelin
2007-10-05  6:28             ` oe for two target boards at the same time Alex
2007-10-05 13:57               ` Cliff Brake
2007-10-05 15:47                 ` Khem Raj
2007-10-06  8:19                 ` Koen Kooi
2007-10-06 11:39                 ` Marcin Juszkiewicz
2007-10-08 20:20                 ` Cliff Brake
2007-10-09  8:28                   ` Koen Kooi
2007-10-09  9:02                     ` pHilipp Zabel
2007-10-09 10:36                       ` Richard Purdie
2007-10-09 11:18                         ` Graeme Gregory
2007-10-09 11:49                           ` Graeme Gregory
2007-10-09 16:52                         ` Paul Sokolovsky
2007-10-09 16:48                   ` Paul Sokolovsky
2007-10-04 18:02           ` monotone/git (was hello...) Richard Purdie
2007-10-04 13:51         ` Michael Krelin
2007-10-04 13:30       ` Michael Krelin
2007-10-04 18:36         ` Chris Larson
2007-10-04 18:49           ` Tim Bird
2007-10-04 18:57             ` Chris Larson
2007-10-04 19:11               ` Michael Krelin
2007-10-04 19:27                 ` Chris Larson
2007-10-04 19:39                   ` Michael Krelin
2007-10-04 20:18                     ` Chris Larson
2007-10-04 20:53                       ` Michael Krelin
2007-10-04 19:08           ` Michael Krelin
2007-10-04 19:28             ` Chris Larson
2007-10-04 13:19     ` hello Michael Krelin
  -- strict thread matches above, loose matches on Subject: below --
2012-08-24  9:14 Hello Giuseppe Longo
2012-08-24  9:47 ` Hello Martin Ertsås
2012-08-24 17:12   ` Hello Giuseppe Longo
2012-08-24 21:14     ` Hello Andrei Gherzan
2012-08-25 15:37       ` Hello Giuseppe Longo
2012-08-25 15:39         ` Hello Andrei Gherzan
2013-06-03 23:23 Hello Tom King

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=1191494488.2516.34.camel@toontown \
    --to=tobias.pflug@gmx.net \
    --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