All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	torvalds@osdl.org, Nigel Cunningham <ncunningham@cyclades.com>,
	linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Re: Linux 2.6.16.14
Date: Tue, 9 May 2006 12:18:28 -0700	[thread overview]
Message-ID: <20060509191828.GL24291@moss.sous-sol.org> (raw)
In-Reply-To: <445F95DC.4050109@tmr.com>

* Bill Davidsen (davidsen@tmr.com) wrote:
> Alistair John Strachan wrote:
> >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.

As a general rule, we do our best to keep in sync.  Typically they go
to mainline first.  A few security patches may bypass that and go in
parallel.  And, of course, anything that's since been redone in mainline
to the point that the patch is not relevant will only live in -stable.

thanks,
-chris

  reply	other threads:[~2006-05-09 19:16 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
2006-05-09 19:18         ` Chris Wright [this message]
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=20060509191828.GL24291@moss.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=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.