public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: brian@worldcontrol.com
To: Patrick Mochel <mochel@osdl.org>
Cc: Pavel Machek <pavel@suse.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: revert to 2.6.0-test3 state
Date: Thu, 4 Sep 2003 21:13:16 -0700	[thread overview]
Message-ID: <20030905041316.GA1886@top.worldcontrol.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0309040820520.940-100000@localhost.localdomain>

On Thu, Sep 04, 2003 at 08:25:38AM -0700, Patrick Mochel wrote:
> No, you have to understand that I don't want to call software_suspend() at 
> all. You've made the choice not to accept the swsusp changes, so we're 
> forking the code. We will have competing implementations of 
> suspend-to-disk in the kernel. 

And the fork happened in 2.6.0-test4?

Some how I thought the 6, being even, meant stable.

I am at a complete loss how these test3 to test4 major changes
that broke everything meet with the often repeated definitions
of how kernel development is to be accomplished.

Perhaps I missed something, development kernels include all
odd numbers and 6?

-- 
Brian Litzinger

  parent reply	other threads:[~2003-09-05  4: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
2003-09-05  4:13       ` brian [this message]
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=20030905041316.GA1886@top.worldcontrol.com \
    --to=brian@worldcontrol.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox