From: "Matt H." <lkml@lpbproductions.com>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: Can swsusp 2.0 be merged into the 2.4 tree
Date: Wed, 10 Dec 2003 14:55:33 -0700 [thread overview]
Message-ID: <200312101455.34154.lkml@lpbproductions.com> (raw)
In-Reply-To: <200312110537.17496.mhf@linuxmail.org>
My personal view is this shouldn't merged. 2.4 shouldn't have more new
features. That's what 2.6 is for.
Matt H.
On Wednesday 10 December 2003 02:39 pm, Michael Frank wrote:
> swsusp is useful feature also for 2.4. Could this please be merged.
>
> Regards
> Michael
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-12-10 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 21:39 RFC: Can swsusp 2.0 be merged into the 2.4 tree Michael Frank
2003-12-10 21:54 ` Mike Fedyk
2003-12-11 19:36 ` Michael Frank
2003-12-10 21:55 ` Matt H. [this message]
2003-12-12 19:22 ` Pavel Machek
2003-12-14 4:38 ` Nigel Cunningham
2003-12-14 11:03 ` 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=200312101455.34154.lkml@lpbproductions.com \
--to=lkml@lpbproductions.com \
--cc=linux-kernel@vger.kernel.org \
/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).