From: Michael Frank <mhf@linuxmail.org>
To: Pavel Machek <pavel@suse.cz>, Rob Landley <rob@landley.net>
Cc: Patrick Mochel <mochel@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>,
Nigel Cunningham <ncunningham@clear.net.nz>,
swsusp-devel <swsusp-devel@lists.sourceforge.net>
Subject: Re: Fix up power managment in 2.6
Date: Fri, 5 Sep 2003 18:56:05 +0800 [thread overview]
Message-ID: <200309051856.05873.mhf@linuxmail.org> (raw)
In-Reply-To: <20030905102628.GB16859@atrey.karlin.mff.cuni.cz>
On Friday 05 September 2003 18:26, Pavel Machek wrote:
> 2.6 swsusp development is not really done on that list.
Oh Really - do I have to dig out the message in which you agreed to consolidate the effort on that list?
Reminds me of when Nigel wrote to Linus for guidance on the development direction of swsusp and you replied...
You have been so nice recently, actually, I am just beginning to wonder on who's payroll your are...
Michael
next prev parent reply other threads:[~2003-09-05 10:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 23:28 Fix up power managment in 2.6 Pavel Machek
2003-09-01 6:57 ` Russell King
2003-09-01 8:11 ` Pavel Machek
2003-09-01 8:26 ` Russell King
2003-09-01 9:33 ` Pavel Machek
2003-09-01 16:28 ` Linus Torvalds
2003-09-01 21:12 ` Pavel Machek
2003-09-01 21:52 ` Russell King
2003-09-01 22:19 ` Pavel Machek
2003-09-01 22:30 ` Russell King
2003-09-01 22:40 ` Pavel Machek
2003-09-01 22:48 ` Russell King
2003-09-02 17:17 ` Greg KH
2003-09-03 15:13 ` Pavel Machek
2003-09-02 10:21 ` Benjamin Herrenschmidt
2003-09-03 13:02 ` Alan Cox
2003-09-03 13:31 ` Benjamin Herrenschmidt
2003-09-03 17:08 ` Pavel Machek
2003-09-05 20:42 ` Pavel Machek
2003-09-01 22:55 ` Patrick Mochel
2003-09-01 23:38 ` Pavel Machek
2003-09-02 0:52 ` Patrick Mochel
2003-09-02 9:02 ` Pavel Machek
2003-09-02 9:47 ` Pavel Machek
2003-09-02 16:11 ` Patrick Mochel
2003-09-03 16:21 ` Pavel Machek
2003-09-03 23:17 ` Patrick Mochel
2003-09-03 17:49 ` Pavel Machek
2003-09-03 17:59 ` bill davidsen
2003-09-03 23:20 ` Patrick Mochel
2003-09-05 9:33 ` Pavel Machek
2003-09-03 20:03 ` Bill Davidsen
2003-09-03 22:14 ` Pavel Machek
2003-09-04 4:06 ` Bill Davidsen
2003-09-04 14:52 ` Patrick Mochel
2003-09-02 10:29 ` Jan Rychter
2003-09-05 5:58 ` Rob Landley
2003-09-05 10:26 ` Pavel Machek
2003-09-05 10:56 ` Michael Frank [this message]
2003-09-05 11:08 ` Pavel Machek
2003-09-05 11:51 ` Michael Frank
2003-09-05 12:01 ` Pavel Machek
2003-09-05 17:47 ` Patrick Mochel
2003-09-05 18:02 ` Jeff Garzik
2003-09-05 18:13 ` Patrick Mochel
2003-09-05 21:46 ` Jeff Garzik
2003-09-05 18:57 ` Rob Landley
2003-09-05 19:06 ` Pavel Machek
2003-09-05 20:09 ` Keyboard stuff (was Re: Fix up power managment in 2.6) Rob Landley
2003-09-05 20:31 ` Pavel Machek
2003-09-05 20:01 ` Fix up power managment in 2.6 Richard A Nelson
2003-09-05 21:45 ` Jeff Garzik
2003-09-05 18:49 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-09-05 20:13 Nicolas Mailhot
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=200309051856.05873.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=ncunningham@clear.net.nz \
--cc=pavel@suse.cz \
--cc=rob@landley.net \
--cc=swsusp-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox