From: Dave Hansen <haveblue@us.ibm.com>
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:03:21 -0800 [thread overview]
Message-ID: <1112137401.27732.58.camel@localhost> (raw)
In-Reply-To: <4249DC03.4000806@tlinx.org>
On Tue, 2005-03-29 at 14:51 -0800, L. A. Walsh 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.
I highly suggest using ketchup for your kernel patching needs:
http://www.selenic.com/ketchup/
Here, I have a plain 2.6.11 kernel that I upgrade to 2.6.11.4. I then
want it to go right to 2.6.11.6.
dave@kernel:~/temp/linux-2.6.11$ ketchup 2.6.11.4
2.6.11 -> 2.6.11.4
Applying patch-2.6.11.4.bz2
dave@kernel:~/temp/linux-2.6.11$ ketchup 2.6.11.6
2.6.11.4 -> 2.6.11.6
Applying patch-2.6.11.4.bz2 -R
Applying patch-2.6.11.6.bz2
dave@kernel:~/temp/linux-2.6.11$
BTW, it also keeps a cache of local patches, and downloads if needed.
So, you'll see the downloads the first time that you use it for any
given patch.
Does that help?
-- Dave
next prev parent reply other threads:[~2005-03-29 23:03 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 [this message]
2005-03-29 23:04 ` Chris Wright
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=1112137401.27732.58.camel@localhost \
--to=haveblue@us.ibm.com \
--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 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.