From: Nigel Cunningham <firstname.lastname@example.org>
To: Pavel Machek <email@example.com>, Jan Rychter <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>
Subject: Re: [Swsusp-devel] Re: [Swsusp] 2.5 suspend.c changes ahead
Date: Sun, 20 Jul 2003 23:20:31 +1200 [thread overview]
Message-ID: <1058700016.1705.4.camel@laptop-linux> (raw)
Longer term, I don't want them to be entirely different beasts. Once I
get swapfile support working for 2.4, I have no plans for further
development. I plan that my next task will be to port it to 2.5/6, and
then begin to seek to merge it with Pavel, Andrew or whoever will take
patces as far as they are willing.
On Sun, 2003-07-20 at 23:10, Pavel Machek wrote:
> > > 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!
> > Pavel> Okay, I should start doing something.
> > >> Swsusp for 2.4 is nearing 1.0.
> > How is 2.5 swsusp going to be related to 2.4 swsusp? I am not sure I
> > understand the relationship -- it seems the two codebases have diverged
> > quite a bit?
> > Is it going to be an entirely different beast?
> Entirely different beast.
495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
-- Romans 5:6, NIV.
next prev parent reply other threads:[~2003-07-20 11:05 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 ` [Swsusp] " Michael Frank
2003-07-09 18:18 ` 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 [this message]
2003-07-21 9:01 ` Pavel Machek
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).