Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@lists.openembedded.org>
Subject: Re: RFC: RW access for polyonymous
Date: Tue, 1 May 2007 23:42:53 +0300	[thread overview]
Message-ID: <361637820.20070501234253@gmail.com> (raw)
In-Reply-To: <f17ves$luc$1@sea.gmane.org>

Hello Rolf,

Tuesday, May 1, 2007, 9:04:10 PM, you wrote:

> 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

> Take a look, comment and decide.

        I support this, and would be happy to peer-review Michael's
commits.

> Regards

> Rolf


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      parent reply	other threads:[~2007-05-01 20:52 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
2007-05-01 20:42 ` Paul Sokolovsky [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=361637820.20070501234253@gmail.com \
    --to=pmiscml@gmail.com \
    --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