From: jbradford@dial.pipex.com
To: linux-kernel@vger.kernel.org
Subject: Docs for 2.4.x -> 2.6.x
Date: Mon, 21 Oct 2002 13:34:10 +0100 (BST) [thread overview]
Message-ID: <200210211234.g9LCYAAf002661@darkstar.example.net> (raw)
Is anybody currently responsible for writing a 2.4.x -> 2.6.x
migration FAQ/HOWTO/guide at all?
I know, in theory, you should just be able to do a 'make oldconfig',
etc, etc, but we really want to encourage people to move from, say,
OSS to ALSA, and to start using things that were experimental in
2.4.x, but not experimental in 2.6.x
If nobody else is already responsible for making such a document, I'd
be quite interested in collecting the necessary info from the various
maintainers, and collating it in to a usable document.
I think it would be quite useful, because without such an effort, I
think that there will be quite a few 2.6.x boxen out there which are
using no new features over 2.4.x, and as a result aren't going to feel
as much of an improvement as they could do.
John.
next reply other threads:[~2002-10-21 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 12:34 jbradford [this message]
2002-10-21 15:31 ` Docs for 2.4.x -> 2.6.x Josh Myer
2002-10-21 15:50 ` jbradford
2002-10-21 15:55 ` Randy.Dunlap
2002-10-21 16:17 ` jbradford
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=200210211234.g9LCYAAf002661@darkstar.example.net \
--to=jbradford@dial.pipex.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