From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: New Developer Access
Date: Fri, 29 Feb 2008 11:26:01 +0100 [thread overview]
Message-ID: <fq8mjp$co6$1@ger.gmane.org> (raw)
In-Reply-To: <20080229093652.17ad566a@cimmeria>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Graeme Gregory schreef:
| I would like to propose a new developer to OE, John Lee.
|
| He already has commit access to OE through the openmoko key but I think
| it is time we welcomed him as his own developer. His work is upto the
| quality we expect of a developer.
Have him send a mtn key to Mickey and me according to the instructions
in http://www.openembedded.org/monotonephrasebook.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHx924MkyGM64RGpERAiT1AJ4wgba8qY31ss7S7dx4zoji3u0YWgCfW/JE
/rSrBQk0mKEEmHGgSOF5tR0=
=kDeJ
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-02-29 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:36 New Developer Access Graeme Gregory
2008-02-29 10:26 ` Koen Kooi [this message]
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='fq8mjp$co6$1@ger.gmane.org' \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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