From: Michael Frank <mhf@linuxmail.org>
To: Pavel Machek <pavel@suse.cz>,
Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Patrick Mochel <mochel@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: revert to 2.6.0-test3 state
Date: Fri, 5 Sep 2003 09:09:20 +0800 [thread overview]
Message-ID: <200309050852.26430.mhf@linuxmail.org> (raw)
In-Reply-To: <20030904193105.GF27650@atrey.karlin.mff.cuni.cz>
On Friday 05 September 2003 03:31, Pavel Machek wrote:
> It puts you in a better position, AFAICS. When code is rewritten
> anyway, "don't fix it if it aint broken" is not so important any
> more -- good for you.
>
> I still hope to avoid two software suspends in 2.6.X.
>
Bah, there may be three implementations now.
On Tuesday 02 September 2003 06:55, Patrick Mochel wrote:
>
> In all actuality, I don't need swsusp. I have a better suspend-to-disk
> implementation that is faster, smaller, and cleaner. I've hesitated
> merging it because I thought swsusp improvements would be more welcome.
> Obviously they're not; or you haven't actually taken the time to read the
> code.
>
This looks like a democratic (darwinistic) approach which will help to get
the best solution for 2.6.
Regards
Michael
next prev parent reply other threads:[~2003-09-05 1:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 19:04 swsusp: revert to 2.6.0-test3 state Pavel Machek
2003-09-03 23:34 ` Patrick Mochel
2003-09-04 11:58 ` Pavel Machek
2003-09-04 15:25 ` Patrick Mochel
2003-09-04 18:26 ` Pavel Machek
2003-09-04 19:55 ` Patrick Mochel
2003-09-04 21:44 ` Nigel Cunningham
2003-09-09 15:34 ` Henning P. Schmiedehausen
2003-09-10 21:50 ` Pavel Machek
2003-09-04 19:28 ` Nigel Cunningham
2003-09-04 19:31 ` Pavel Machek
2003-09-05 1:09 ` Michael Frank [this message]
2003-09-05 4:13 ` brian
2003-09-05 5:53 ` Michael Frank
2003-09-05 10:32 ` Pavel Machek
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=200309050852.26430.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 \
/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.