All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	torvalds@osdl.org
Subject: Re: Linux 2.6.16.14
Date: Mon, 08 May 2006 15:02:52 -0400	[thread overview]
Message-ID: <445F95DC.4050109@tmr.com> (raw)
In-Reply-To: <200605050347.51703.s0348365@sms.ed.ac.uk>

Alistair John Strachan wrote:
> On Friday 05 May 2006 03:33, Chris Wright wrote:
>> * Nigel Cunningham (ncunningham@cyclades.com) wrote:
>>> Is this supposed to be some sort of subtle pressure on Linus to open 2.7?
>>> :>
>> He does every couple months and leaves it open for a few weeks.
>> Then, just to keep us guessing, he releases it with a 2.6 name ;-)
>>
>> Actually, I think the system is working quite well.  We've got a quick
>> route for getting bug fixes and security fixes to users, and a shorter
>> devel cycle helping distro folks get more regular drops from upstream.
> 
> I think it's working extremely well. When it comes to security fixes, I want 
> them as soon as possible. There's no sense batching them.
> 
> The only thing to be careful of is that -stable fixes (or complete reworks) 
> get merged with mainline, so the trees don't go out of sync. So far this 
> seems to have been OK.
> 
As I recall these patches may or may not go into mainline. The next full 
release may address the problem in a whole new way.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


  reply	other threads:[~2006-05-09 14:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05  0:35 Linux 2.6.16.14 Chris Wright
2006-05-05  0:42 ` Chris Wright
2006-05-05  1:52 ` Nigel Cunningham
2006-05-05  2:20   ` Ioan Ionita
2006-05-05  2:33   ` Chris Wright
2006-05-05  2:47     ` Alistair John Strachan
2006-05-08 19:02       ` Bill Davidsen [this message]
2006-05-09 19:18         ` [stable] " Chris Wright
2006-05-05  3:03     ` Nigel Cunningham
2006-05-05  3:18       ` Ioan Ionita
2006-05-05  3:42         ` Patrick McFarland
2006-05-05  3:25       ` Chris Wright
2006-05-05  3:33         ` CaT
2006-05-05  5:10           ` [stable] " Greg KH
2006-05-05  4:50       ` Willy Tarreau
2006-05-05  5:02         ` Nigel Cunningham
2006-05-05  5:20           ` Willy Tarreau
2006-05-05 13:29 ` Josh Boyer
2006-05-05 17:40   ` Chris Wright

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=445F95DC.4050109@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=stable@kernel.org \
    --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 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.