From: Brian Gerst <bgerst@didntduck.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question re the dot releases such as 2.6.12.3
Date: Mon, 25 Jul 2005 12:38:43 -0400 [thread overview]
Message-ID: <42E51593.7070902@didntduck.org> (raw)
In-Reply-To: <200507251020.08894.gene.heskett@verizon.net>
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.
--
Brian Gerst
next prev parent reply other threads:[~2005-07-25 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 14:20 Gene Heskett
2005-07-25 16:38 ` Brian Gerst [this message]
2005-07-25 21:53 ` Gene Heskett
2005-07-27 1:28 ` Kurt Wall
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=42E51593.7070902@didntduck.org \
--to=bgerst@didntduck.org \
--cc=gene.heskett@verizon.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®