From: Michael Frank <mflt1@micrologica.com.hk>
To: Pavel Machek <pavel@suse.cz>, kernel list <linux-kernel@vger.kernel.org>
Cc: swsusp-devel <swsusp-devel@lists.sourceforge.net>,
swsusp@lister.fornax.hu
Subject: Re: [Swsusp] 2.5 suspend.c changes ahead
Date: Wed, 9 Jul 2003 19:59:45 +0800 [thread overview]
Message-ID: <200307091940.52781.mflt1@micrologica.com.hk> (raw)
In-Reply-To: <20030708233507.GB140@elf.ucw.cz>
On Wednesday 09 July 2003 07:35, Pavel Machek wrote:
> Hi!
>
> I guess I'll do some big kernel/suspend.c changes tommorow. If you
> have some changes pending, please submit them within next 10 hours (I
> can't code while I sleep ;-).
> Pavel
Looking forward!
Swsusp for 2.4 is nearing 1.0.
Swsusp activities have moved to sourceforge as Florent's pages are no longer
updated and he also took leave of absence. Florent also mentioned in one of
his last posts that the old swsusp mailing list at fornax may evaporate any
time.
Could we please use the new mailing list <swsusp-devel@lists.sourceforge.net>
as well as the download area there (link below)?
Regards
Michael
--
Powered by linux-2.5.74-mm1. Compiled with gcc-2.95-3 - mature and rock solid
My current linux related activities:
- 2.5 yenta_socket testing
- Test development and testing of swsusp for 2.4/2.5 and ACPI S3 of 2.5 kernel
- Everyday usage of 2.5 kernel
More info on 2.5 kernel: http://www.codemonkey.org.uk/post-halloween-2.5.txt
More info on swsusp: http://sourceforge.net/projects/swsusp/
next prev parent reply other threads:[~2003-07-09 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 23:35 2.5 suspend.c changes ahead Pavel Machek
2003-07-09 2:43 ` Nigel Cunningham
2003-07-09 11:59 ` Michael Frank [this message]
2003-07-09 18:18 ` [Swsusp] " Pavel Machek
2003-07-09 19:28 ` [Swsusp-devel] " Nigel Cunningham
2003-07-13 5:08 ` Jan Rychter
2003-07-20 11:10 ` Pavel Machek
2003-07-20 11:20 ` Nigel Cunningham
2003-07-21 9:01 ` 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=200307091940.52781.mflt1@micrologica.com.hk \
--to=mflt1@micrologica.com.hk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=swsusp-devel@lists.sourceforge.net \
--cc=swsusp@lister.fornax.hu \
/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).