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: Sat, 19 Jan 2008 20:29:39 +0200 [thread overview]
Message-ID: <404027028.20080119202939@gmail.com> (raw)
In-Reply-To: <fmqnta$9lc$1@ger.gmane.org>
Hello Rolf,
Friday, January 18, 2008, 7:33:30 PM, you wrote:
> Paul Sokolovsky schrieb:
>>> 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 ;-).
> OK, everyone is entitled to their opinion, fair enough.
> I am sure you will then afford me the liberty to completely ignore any
> and all comments you make which I deem to be in inappropriate style, no
> matter how technically valid. I have seen enough of it, I don't want it
> anymore, I will block it out from my perception.
I recommend you to stop declaring attitudes of ignore and alienation
towards OE community (re: http://lists.linuxtogo.org/pipermail/openembedded-devel/2007-December/003753.html)
and its individual members (which you do almost every time somebody
don't agree with what you do).
If you have something with the tone of my messages, ignoring it is
what I myself recommend you to do, especially if you tend to perceive
it on the negative side. But I don't recommend you to ignore technical
content of anybody's comments - you had your commits reverted multiple
times, and it's time to learn what's wrong.
> IOW, next time it will be *you* doing
> http://oz.leggewie.org/wip/wifi-suspend.patch Fair enough, I'd say.
And I'm glad you're now getting idea on that. Except that there
shouldn't be "you" or "me". Instead, anytime you're not sure if some
change is done the best way and if it doesn't regress something (and
please always give anyone - including yourself - power of doubt),
please consult with wider community. As was told many times already,
IRC is a bad place for RFCs. It's oftentimes not easy to decide if
some change requires RFC or not, so being conservative and posting an
RFC still is a good plan. Otherwise, be prepared that your change may
break something you couldn't even think (OE is a complex system), so
you may be asked to re-do your solution, or have it reverted until you
come up with better plan. Finally, don't haste with either applying
patches without RFCing them wide enough, or with applying them without
letting people some time to review RFC.
Those were suggestions I myself used to get, and now hopefully trying
to follow. I'm sorry if you hear them not the first time - I would
think that is the case actually. I'm even more sorry if you didn't
have chance to see them before - then it for sure was mistake to start
commenting on your commit with technical matters, I should have
started with that instead.
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2008-01-19 18:21 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
2008-01-18 17:33 ` Rolf Leggewie
2008-01-19 18:29 ` Paul Sokolovsky [this message]
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=404027028.20080119202939@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.