From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"Arjan van de Ven" <arjanv@redhat.com>,
"Jon Smirl" <jonsmirl@yahoo.com>,
dri-devel <dri-devel@lists.sourceforge.net>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>
Subject: Re: [Dri-devel] 2.6 kernel change in nopage
Date: Fri, 02 Jan 2004 09:57:36 +1300 [thread overview]
Message-ID: <1072990656.25583.18.camel@laptop-linux> (raw)
In-Reply-To: <Pine.LNX.4.58.0401011205110.2065@home.osdl.org>
On Fri, 2004-01-02 at 09:19, Linus Torvalds wrote:
> In contrast, full-file interfaces for different kernel versions are a
> _lot_ easier to merge and keep track of. They may look like "duplication",
> but the advantages are legion. You don't mix different OS's and different
> versions together, and that makes it much easier to support them all
> without going crazy.
Of course there are also advantages to _not_ using the file-per-kernel
version scheme. Keeping one set of files means time is not wasted
applying the same change to multiple variations, removes the possibility
of patches getting applied to one version and not another and simplifies
the process of continuing to support old kernel versions. For merging, a
bit of test processing on the files could always be used to remove the
ugliness and clean things up.
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
next prev parent reply other threads:[~2004-01-01 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031231182148.26486.qmail@web14918.mail.yahoo.com>
2004-01-01 12:03 ` [Dri-devel] 2.6 kernel change in nopage Michel Dänzer
2004-01-01 12:10 ` Arjan van de Ven
2004-01-01 12:23 ` Michel Dänzer
2004-01-01 12:28 ` Arjan van de Ven
2004-01-01 14:27 ` Michel Dänzer
2004-01-01 15:06 ` William Lee Irwin III
2004-01-01 20:19 ` Linus Torvalds
2004-01-01 20:57 ` Nigel Cunningham [this message]
2004-01-01 22:57 ` Linus Torvalds
2004-01-10 21:54 ` Michel Dänzer
2004-01-10 22:08 ` Arjan van de Ven
2004-01-11 0:15 ` Michel Dänzer
2004-01-01 13:33 ` William Lee Irwin III
2004-01-01 13:50 ` Michel Dänzer
2004-01-01 14:13 ` William Lee Irwin III
2004-01-01 17:55 ` Alan Cox
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=1072990656.25583.18.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel@daenzer.net \
--cc=torvalds@osdl.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