All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@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 15:34:41 +0100	[thread overview]
Message-ID: <fmnp24$rob$1@ger.gmane.org> (raw)
In-Reply-To: <1012527691.20080117145250@gmail.com>


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
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.

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?  FOSS is an incremental process.

I am willing to get this not only right for me, but to everyone's
satisfaction.  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.




  reply	other threads:[~2008-01-17 14:34 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 [this message]
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
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='fmnp24$rob$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.