Sam, my patch to automatically include a random value based upon the
BitKeeper or CVS version in the kernel version had one, rather minor,
bug related to building in seperate object and source trees.
This patch fixes that up.
Signed-Off-By: Ryan Anderson <[EMAIL PROTECTED]>
Index: local-quilt/sc
Sam, this version includes the CVS portion.
Automatically append a semi-random version if the tree we're building
isn't tagged in BitKeeper or CVS and CONFIG_LOCALVERSION_AUTO is set.
This fixes the case when Linus (or someone else) does a release and tags
it, someone else does a build of that
Automatically append a semi-random version if the tree we're building
isn't tagged in BitKeeper (or another SCM) and CONFIG_LOCALVERSION_AUTO
is set.
This fixes the case when Linus (or someone else) does a release and tags
it, someone else does a build of that release tree (i.e, 2.6.11), and
insta
Snipping a bit as I go, thanks for the feedback, Sam.
On Mon, Mar 14, 2005 at 11:43:17PM +0100, Sam Ravnborg wrote:
> On Wed, Mar 09, 2005 at 03:06:38AM -0500, Ryan Anderson wrote:
> > Two approachs are present here, a Perl version that is setup to handle
> > other automatic version appends (i.e,
On Wed, Mar 09, 2005 at 03:06:38AM -0500, Ryan Anderson wrote:
> Automatically append a semi-random version if the tree we're building
> isn't tagged in BitKeeper and CONFIG_LOCALVERSION_AUTO is set.
>
> This fixes the case when Linus (or someone else) does a release and tags
> it, someone else do
Automatically append a semi-random version if the tree we're building
isn't tagged in BitKeeper and CONFIG_LOCALVERSION_AUTO is set.
This fixes the case when Linus (or someone else) does a release and tags
it, someone else does a build of that release tree (i.e, 2.6.11), and
installs it. Later, b
6 matches
Mail list logo
