public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "L. A. Walsh" <lkml@tlinx.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: 2.6.release.patchlevel:  Patch against 2.6.release[.0] ?
Date: Tue, 29 Mar 2005 15:04:36 -0800	[thread overview]
Message-ID: <20050329230436.GQ28536@shell0.pdx.osdl.net> (raw)
In-Reply-To: <4249DC03.4000806@tlinx.org>

* L. A. Walsh (lkml@tlinx.org) wrote:
> Given the frequency with which stabilization patches may be released, it
> may not be practical to expect users to catch each release announcement
> and download each patch.
> 
> Especially if small patches are released for stability, as one might
> (hopefully) expect.  Assuming that stability and "fix-it" patches will
> generally be small (I'd hope).  Seeing that the latest "fix-it" patch
> is already at ".6", I'd have to load multiple patches to catch up from
> 2.6.11.  I blinked my eyes and missed a few or 5 previous stability
> patches, so I just downloaded the entire bzip...not a biggie, but
> might create less load on servers if I didn't need to go through 6
> patch applications to get current.

The patches on kernel.org in v2.6/ are already against the base (i.e.
patch-2.6.11.6.bz2 is against 2.6.11).  The patches in v2.6/incr/
are incremental between -stable releases (i.e. patch-2.6.11.5-6.bz2 is
against 2.6.11.5).

thanks,
-chris

  parent reply	other threads:[~2005-03-29 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 22:51 RFC: 2.6.release.patchlevel: Patch against 2.6.release[.0] ? L. A. Walsh
2005-03-29 22:58 ` Randy.Dunlap
2005-03-29 23:03 ` Dave Hansen
2005-03-29 23:04 ` Chris Wright [this message]
2005-03-31  2:20   ` L. A. Walsh

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=20050329230436.GQ28536@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.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