From: Kurt Wall <kwall@kurtwerks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Question re the dot releases such as 2.6.12.3
Date: Tue, 26 Jul 2005 21:28:53 -0400 [thread overview]
Message-ID: <20050727012853.GA2354@kurtwerks.com> (raw)
In-Reply-To: <42E51593.7070902@didntduck.org>
On Mon, Jul 25, 2005 at 12:38:43PM -0400, Brian Gerst took 21 lines to write:
> Gene Heskett wrote:
> >Greetings;
> >
> >I just built what I thought was 2.6.12.3, but my script got a tummy
> >ache because I didn't check the Makefile's EXTRA_VERSION, which was
> >set to .2 in the .2 patch. Now my 2.6.12 modules will need a refresh
> >build. :(
> >
> >So whats the proper patching sequence to build a 2.6.12.3?
> >
>
> The dot-release patches are not incremental. You apply each one to the
> base 2.6.12 tree.
This bit me a while back, too. I'll submit a patch to the top-level
README to spell it out.
Kurt
--
You cannot propel yourself forward by patting yourself on the back.
next prev parent reply other threads:[~2005-07-27 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 14:20 Question re the dot releases such as 2.6.12.3 Gene Heskett
2005-07-25 16:38 ` Brian Gerst
2005-07-25 21:53 ` Gene Heskett
2005-07-27 1:28 ` Kurt Wall [this message]
2005-07-27 1:50 ` Steven Rostedt
2005-07-27 2:34 ` Valdis.Kletnieks
2005-07-27 11:11 ` Steven Rostedt
2005-07-27 3:25 ` Gene Heskett
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=20050727012853.GA2354@kurtwerks.com \
--to=kwall@kurtwerks.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.