All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: will someone make 2.6.39.* a longterm ?
Date: Wed, 3 Aug 2011 17:54:23 -0700	[thread overview]
Message-ID: <20110804005423.GA28005@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1108031648510.21707@filesrv1.baby-dragons.com>

On Wed, Aug 03, 2011 at 04:51:03PM -0800, Mr. James W. Laferriere wrote:
> 	Hello Greg ,
> 
> On Wed, 3 Aug 2011, Greg KH wrote:
> >On Wed, Aug 03, 2011 at 12:05:58PM -0800, Mr. James W. Laferriere wrote:
> >>	Hello All ,  Is anyone looking at making 2.6.39.* into a longterm
> >>stable ?
> >
> >No, why would they?
> >
> >Or, to turn it the other way, why do you feel .39 would be a viable
> >longer kernel to maintain?  What are you using it for that requires it
> >to be handled in this manner?
> >thanks,
> >greg k-h
> 	Probably no reason at all ,  But ...  It is the final 2.6 kernel version .

But what does that really mean?  There is no "real" difference between
2.6.39 and 3.0 that is not the same difference between 2.6.38 and
2.6.39.

> 	With 3.0 being released there will only be Yours & the others
> maintaining the 2.6.<39 otherwise .

Is that a problem?

> 	Ego I guess .

Whose?

confused.

greg k-h

  reply	other threads:[~2011-08-04  0:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 20:05 will someone make 2.6.39.* a longterm ? Mr. James W. Laferriere
2011-08-03 23:26 ` Greg KH
2011-08-04  0:51   ` Mr. James W. Laferriere
2011-08-04  0:54     ` Greg KH [this message]
2011-08-06  9:38     ` david

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=20110804005423.GA28005@kroah.com \
    --to=greg@kroah.com \
    --cc=babydr@baby-dragons.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 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.