From: Roman I Khimov <roman@khimov.ru>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Write access for Roman I Khimov
Date: Tue, 23 Mar 2010 21:01:34 +0300 [thread overview]
Message-ID: <201003232101.37576.roman@khimov.ru> (raw)
In-Reply-To: <201003231851.37447.marcin@juszkiewicz.com.pl>
[-- Attachment #1: Type: Text/Plain, Size: 1176 bytes --]
В сообщении от Вторник 23 марта 2010 20:51:32 автор Marcin Juszkiewicz
написал:
> I would like to give write access for Roman I Khimov. His patches are good
> (new recipes could get descriptions in commit log anyway) and he touched
> ugly beast (Perl I mean) and survived.
Hey, I've already got one. ;)
http://lists.linuxtogo.org/pipermail/openembedded-devel/2009-April/009972.html
It's just that I was so busy with our internal projects that I didn't have any
time for community work till now. Now we've made a major release and currently
in early stage of starting a new version, so currently I'm syncing with OE.dev
and I regret that I didn't have time when I've made things internally, since
it's hell. But we've also changed some internal processes so that with new
version of our product we'll be closer to upstream and will be pushing things
earlier.
Thanks, anyway! ;)
P.S. As for descriptions, I've thought that having them in recipes is enough,
but I could add those in commit messages if there is a need for it.
--
http://roman.khimov.ru
mailto: roman@khimov.ru
gpg --keyserver hkp://subkeys.pgp.net --recv-keys 0xE5E055C3
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2010-03-23 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 17:51 [RFC] Write access for Roman I Khimov Marcin Juszkiewicz
2010-03-23 18:01 ` Roman I Khimov [this message]
2010-03-23 18:26 ` Roman I Khimov
2010-03-23 18:15 ` Stefan Schmidt
2010-03-23 18:19 ` Stefan Schmidt
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=201003232101.37576.roman@khimov.ru \
--to=roman@khimov.ru \
--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.