From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Patrick Mochel <mochel@digitalimplant.org>,
Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Suspend development list <swsusp-devel@lists.sourceforge.net>
Subject: Re: The verdict on the future of suspending to disk?
Date: Wed, 17 Mar 2004 09:13:15 +1300 [thread overview]
Message-ID: <1079467995.3403.68.camel@calvin.wpcb.org.au> (raw)
In-Reply-To: <20040316113717.GB2282@elf.ucw.cz>
Hi.
On Wed, 2004-03-17 at 00:37, Pavel Machek wrote:
> I do not think Patrick is going to maintain anything.
>
> If you want to maintain it, you can have it. Big plus if you are able
> to deal with Patrick.
Okay, but can we clearly delineate responsibilities? I'm happy to deal
with the suspend-to-disk stuff because I understand it. I don't however
understand suspend-to-ram or kobjects (yes, I will need to learn them)
or device drivers, so I don't want anyone thinking I'm going to
concentrate on anything more than what I'm already doing. That said, I'd
love to take over software suspend and work on merging the work I've
done.
Nigel
--
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6253 0250 (home)
Evolution (n): A hypothetical process whereby infinitely improbable events occur
with alarming frequency, order arises from chaos, and no one is given credit.
prev parent reply other threads:[~2004-03-16 22:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 3:38 Nigel Cunningham
2004-03-16 8:05 ` [Swsusp-devel] " Karol Kozimor
2004-03-16 11:37 ` Pavel Machek
2004-03-16 12:15 ` Pavel Machek
2004-03-16 13:38 ` [Swsusp-devel] " Michael Frank
2004-03-16 15:10 ` Pavel Machek
2004-03-16 20:28 ` Nigel Cunningham
2004-03-16 20:13 ` Nigel Cunningham [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=1079467995.3403.68.camel@calvin.wpcb.org.au \
--to=ncunningham@users.sourceforge.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@ucw.cz \
--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
all inboxes | Powered by JetHome®