All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rolf Leggewie <no2spam@nospam.arcornews.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664.
Date: Thu, 17 Jan 2008 17:23:27 +0200	[thread overview]
Message-ID: <1179311965.20080117172327@gmail.com> (raw)
In-Reply-To: <fmnp24$rob$1@ger.gmane.org>

Hello Rolf,

Thursday, January 17, 2008, 4:34:41 PM, you wrote:

> Paul,

> thank you for pointing out the problem and a template solution towards
> the end of your initial rant as well.  In fact I am already working on

  Thanks for acting on that.

> moving the mid-term fix into a separate package to provide an even less
> intrusive mid-term fix ->
> http://oz.leggewie.org/wip/wifi-suspend.patch



> But...

> Paul Sokolovsky schrieb:
>> and of course they need to be supported still, and right now. The question
>> is how that is done - if it comes mixed into one big mess
>                                                        ^^^^
>> I don't appreciate someone moving in the opposite direction just to solve on-spot problem. OE is
>     ^^^^^^^^^^^^^^^^
>> powerful environment allowing to solve make focused, maintainable and
>> reusable changes - even if they're workarounds, and people should
>> learn to use them.

> And I don't appreciate after I have

> * fixed a real usability issue which likely strongly influences the
>   perception of OE-derived distros
> * consulted with a *LOT* of people on IRC and in the bug tracker over
>   several days
> * have put quite some time into finding an acceptable solution for
>   everyone

> that someone comes around who had previously been quiet on this and then
> calls my work a "mess" and generally finds very unappreciative words for
> what I've done and the time I've spent.

  Oh, do we need a bit of affirmative action here again? ;-) Ok, so
"mess" is not your work, it's what core layer of OE runtime is, to the large
extent. Being with OE for quite some time, I know such
problem areas, and try to work towards resolving them. That's hard to
do on one's own, so I humbly expects that other experienced OE
developers to share such approach, instead of trying to apply pain-of-day
patches, just increasing existing mess.

 As for IRC, unfortunately, I don't have much time to be on it
lately, but I try to be on MLs. So, don't get too hot about receiving
*one more* comment if you already received them a lot. OE is big system,
and noone can know and be up to date with all its areas.

> Mickey's comment

> # I agree. The issue to fix is worthwile, but I would prefer seperate
> # packaging as well.

> sounds quite different, don't you agree?

  Nope, I don't ;-). I don't see anything special about communication
which goes your way, no matter who's the other side, sorry ;-).

> FOSS is an incremental process.

> I am willing to get this not only right for me, but to everyone's
> satisfaction.

  Great, so I just provide my comments on the matter. You may wonder
how it gets often that you and I get into communication (though I of
course give comments to other people too). But even that should be
rather clear - because we both care about almost the same area
regarding OE, albeit with different approaches and plans. In this
regard, I appreciate your review, suggestions, and comments!

> But I kindly want to ask you to consider that it is not
> only what you say but also how you say it.

> PS: I don't intend to and hope I did not start another flame war, but
> this is important to me.


  Just in case, there's still personal mail around...


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




  parent reply	other threads:[~2008-01-17 15:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1JF7vM-0000k1-Mc@linuxtogo.org>
2008-01-17 11:18 ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Paul Sokolovsky
2008-01-17 11:57   ` Bug ohviey1
2008-01-17 12:01   ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Michael 'Mickey' Lauer
2008-01-17 12:22   ` Koen Kooi
2008-01-17 12:52     ` Paul Sokolovsky
2008-01-17 14:34       ` Rolf Leggewie
2008-01-17 15:09         ` Mike (mwester)
2008-01-17 15:59           ` Paul Sokolovsky
2008-01-17 17:52             ` Mike (mwester)
2008-01-17 15:23         ` Paul Sokolovsky [this message]
2008-01-18 17:33           ` Rolf Leggewie
2008-01-19 18:29             ` Paul Sokolovsky
2008-01-21 11:16               ` Rolf Leggewie
2008-01-18 18:28         ` Rolf Leggewie

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=1179311965.20080117172327@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=no2spam@nospam.arcornews.de \
    --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.