All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Commit access
Date: Fri, 26 Feb 2010 20:25:42 +0100	[thread overview]
Message-ID: <hm977m$bvo$1@dough.gmane.org> (raw)
In-Reply-To: <fca63bcf1002261053s33343b5r7a79495dce1a9118@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The patches look good and Michael is really good at asking people for
advice, so he gets my vote!

On 26-02-10 19:53, Michael Lippautz wrote:
> Hej all (again),
> 
> I am hereby asking, if I can get commit access to OE.
> 
> (Don't want to go on peoples nerves using irc all the time ;p)
> 
> Some patches: http://cgit.openembedded.org/cgit.cgi/openembedded/log/?qt=author&q=michael+lippautz
> I am currently mostly interested (work related) into
> perl/python/webaccess and gps related stuff.
> 
> Regards,
> Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLiCA1MkyGM64RGpERAoDbAKCW/fia1FkLlV8DtWccGE4P+qPRcwCgnbVs
BlhOB1bogxz7qaT+MpZKcwU=
=o129
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-02-26 19:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 18:53 Commit access Michael Lippautz
2010-02-26 19:25 ` Koen Kooi [this message]
2010-02-26 20:18 ` Denys Dmytriyenko
2010-02-26 21:20 ` Cliff Brake
2010-02-27 11:27   ` Frans Meulenbroeks
  -- strict thread matches above, loose matches on Subject: below --
2010-02-24 20:39 Thomas Zimmermann
2010-02-24 20:45 ` Denys Dmytriyenko
2010-02-24 21:01 ` Martin Jansa
2010-02-24 21:14 ` Klaus Kurzmann
2010-02-25 13:31 ` Cliff Brake
2009-10-29  9:42 Martin Jansa
2009-10-29 10:16 ` Marcin Juszkiewicz
2009-10-29 10:48   ` Graeme Gregory
2009-10-29 10:56 ` Sebastian Spaeth
2009-10-29 14:41 ` Cliff Brake
2009-10-29 17:27   ` Otavio Salvador

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='hm977m$bvo$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.