All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: should in-tree kernel source accommodate older kernel versions?
Date: Tue, 17 Jul 2007 21:46:05 +0000	[thread overview]
Message-ID: <20070717214604.GJ14791@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707171718450.18509@localhost.localdomain>

On Tue, Jul 17, 2007 at 05:36:45PM -0400, Robert P. J. Day wrote:
> On Tue, 17 Jul 2007, Matthew Wilcox wrote:
> > On Tue, Jul 17, 2007 at 05:22:56PM -0400, Robert P. J. Day wrote:
> > >   should kernel source that's in the current source tree still try to
> > > accommodate older kernel versions?  as an example, this is from
> >
> > This has been discussed before, and the current thinking is to
> > remove support for versions of the kernel older than 2.6.0.
> 
> *that* part was self-evident.  i'm talking more specifically about
> older versions of 2.6.x, in particular features that aren't even
> *supported* anymore in the current tree.

You'll find people very resistant to patches that remove support for
older 2.6.x kernels.

-- 
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  parent reply	other threads:[~2007-07-17 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 21:22 should in-tree kernel source accommodate older kernel versions? Robert P. J. Day
2007-07-17 21:33 ` Matthew Wilcox
2007-07-17 21:36 ` Robert P. J. Day
2007-07-17 21:46 ` Matthew Wilcox [this message]
2007-07-18  9:53 ` Robert P. J. Day

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=20070717214604.GJ14791@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.