All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Sergey Lapin <slapinid@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Palms commits.
Date: Wed, 11 Jul 2007 00:08:36 +0300	[thread overview]
Message-ID: <1782937254.20070711000836@gmail.com> (raw)
In-Reply-To: <4693D9F4.5030000@gmail.com>

Hello Sergey,

Tuesday, July 10, 2007, 10:11:48 PM, you wrote:

[]

>>   Summing up, by investing 50% more effort into that, there can be 5
>> times more outcome. And as a "fresh blood" in OE, you're in good
>> position to lead this, as other developers are of course stuck with
>> other issues.

> Do you count yourself in this 50%, btw?

  Absolutely. I contemplated such a change for a long time, actually
current work on adding missing hh.org machine to OE and switching to
defconfiman kernel configuration management are initial steps on that
way. I didn't proceed with OE machine configs cleanup, because well,
it takes some real world dataset to make it general enough, and
because HH.org kernel project was literally the only stakeholder for
such changes, with couple of dozens of machines and counting (whereas
even Zaurus project has around half-dozen architecturally different
machines). So, I eagerly awaited other projects, like Hackhdev to join
more actively with OE, to tackle these issues together.

  I understand your worktime constraints, and the need to get practice
with OE and mtn, but there're other creative ways to get it - like,
for example, adding support for other 8 or so Palm devices in addition
to 4 already in OE. This would be pretty worthy a job for Palm devices
maintainer, and at the same time would happen to give us mentioned raw
dataset to base firm decisions on. And there's also good chance for us
to get in sync, so all Palm and PocketPC devices are in OE, that can't
be checked off for both projects, and we can proceed further with
better support and maintenance facilitation. Of course, this all is
from my side of view, YMMV.

> Best regards,

> S.



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




  parent reply	other threads:[~2007-07-10 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 15:45 [RFC] Palms commits Sergey Lapin
2007-07-10 18:16 ` Paul Sokolovsky
2007-07-10 19:11   ` Sergey Lapin
2007-07-10 19:58     ` Michael Krelin
2007-07-10 21:08     ` Paul Sokolovsky [this message]
2007-07-10 21:01 ` Richard Purdie
2007-07-11 12:59   ` Sergey Lapin

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=1782937254.20070711000836@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=slapinid@gmail.com \
    /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.