From: Pavel Machek <pavel@ucw.cz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: "linux-power" tree [was Re: swsusp updates]
Date: Sun, 27 Jul 2003 00:32:58 +0200 [thread overview]
Message-ID: <20030726223258.GO266@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0307261422080.23977-100000@cherise>
Hi!
> And, that's a real problem with swsusp. It's a huge mess right now. I'd
> like to see it work well and reliably for 2.6, and have the source code be
> in a state where people can look at it without running away screaming.
> Convoluted updates are not going to help the situation.
Okay, so the debate is not over. It looks like his internet connection
only works as long as you keep flaming him -- perhaps he has frozen
ethernet cable? :-)
Anyway, patrick seems to have his own "linux-power" tree, and thinks
that his "linux-power" tree will help powermanagment in Linux. I don't
think that is the case, but I'll provide split patches *once*. Then
I'm going to post each new patch (I guess I'll cc: patrick), but
cumulate them for submission to Linus. Patches will be marked [PM]
(read it as Pavel Machek or Power Managment).
I hope that works for everybody.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
prev parent reply other threads:[~2003-07-26 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 20:45 swsusp updates Pavel Machek
2003-07-26 21:05 ` Patrick Mochel
2003-07-26 21:03 ` Pavel Machek
2003-07-26 21:09 ` Patrick Mochel
2003-07-26 21:13 ` Pavel Machek
2003-07-26 21:31 ` Patrick Mochel
2003-07-26 21:35 ` Pavel Machek
2003-07-26 21:37 ` Pavel Machek
2003-07-26 22:32 ` Pavel Machek [this message]
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=20030726223258.GO266@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).