public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4 <-> 2.6 compatibility
Date: Sun, 26 Oct 2003 16:18:33 +0100	[thread overview]
Message-ID: <yw1xvfqcf2nq.fsf@kth.se> (raw)
In-Reply-To: 20031026150544.GJ15838@merlin.emma.line.org

Matthias Andree <matthias.andree@gmx.de> writes:

> To enlarge the testing base, it would be good if people could just drop
> a 2.6 kernel, some user-space updates and then dual-boot 2.4 and 2.6
> hassle free at will without worrying about a dozen 2.4 kernel patches to
> make it compatible with the new user space.

I've been doing that for months.

-- 
Måns Rullgård
mru@kth.se


  reply	other threads:[~2003-10-26 15:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-25 19:09 Linux 2.6.0-test9 Linus Torvalds
2003-10-25 19:52 ` Marcelo Tosatti
2003-10-25 20:14 ` viro
2003-10-25 22:35   ` Linus Torvalds
2003-10-25 23:45 ` Jose Luis Domingo Lopez
2003-10-26  0:22 ` 2.6.0-test9: selinux compile error with "make O=..." Adrian Bunk
2003-10-26  9:49   ` Sam Ravnborg
2003-10-27 13:40     ` Stephen Smalley
2003-10-27 18:42       ` Sam Ravnborg
2003-10-28 15:10         ` Stephen Smalley
2003-10-26 12:05 ` Linux 2.6.0-test9 Patrik Wallstrom
2003-10-27 18:21   ` Patrik Wallstrom
2003-10-27 22:51     ` bill davidsen
2003-10-28  2:12       ` Jeff Garzik
2003-10-28  4:52         ` Bill Davidsen
2003-10-26 15:05 ` Linux 2.4 <-> 2.6 compatibility (was: Linux 2.6.0-test9) Matthias Andree
2003-10-26 15:18   ` Måns Rullgård [this message]
2003-10-27  2:51     ` Linux 2.4 <-> 2.6 compatibility Matthias Andree
2003-10-26 16:06   ` Jochen Hein
2003-10-26 17:47     ` Fabio Massimo Di Nitto
2003-10-26 18:18       ` Jochen Hein
2003-10-27 16:02 ` Linux 2.6.0-test9 (compile stats) John Cherry

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=yw1xvfqcf2nq.fsf@kth.se \
    --to=mru@kth.se \
    --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