From: Matthias Hentges <oe@hentges.net>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@lists.openembedded.org>
Subject: Re: RFC: RW access for polyonymous
Date: Tue, 01 May 2007 20:20:26 +0200 [thread overview]
Message-ID: <1178043626.23506.8.camel@localhost.localdomain> (raw)
In-Reply-To: <f17ves$luc$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Am Dienstag, den 01.05.2007, 20:04 +0200 schrieb Rolf Leggewie:
> Hi,
>
> with the amount (and speed!) of patches being provided by Michael
> 'polyonymous' Krelin I think it makes sense to give him RW access to OE.
> His bugs are at http://tinyurl.com/2llfhw
I agree, it's about time ;)
--
Matthias 'CoreDump' Hentges
Cologne / Germany
Webmaster of Hentges.net & Embedded Linux Developer
GPG -> gpg --keyserver gpg-keyserver.de --recv-keys 0xAF3030D9
My OS: Debian SID: Geek by Nature, Linux by Choice
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2007-05-01 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:04 RFC: RW access for polyonymous Rolf Leggewie
2007-05-01 18:20 ` Matthias Hentges [this message]
2007-05-01 20:42 ` Paul Sokolovsky
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=1178043626.23506.8.camel@localhost.localdomain \
--to=oe@hentges.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 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.