[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200907292028.32320.elendil@planet.nl>
Date: Wed, 29 Jul 2009 20:28:29 +0200
From: Frans Pop <elendil@...net.nl>
To: Gene Heskett <gene.heskett@...izon.net>
Cc: alan@...rguk.ukuu.org.uk, torvalds@...ux-foundation.org,
hirofumi@...l.parknet.co.jp, aneesh.kumar@...ux.vnet.ibm.com,
rjw@...k.pl, ray-lk@...rabbit.org, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, stern@...land.harvard.edu
Subject: Re: [PATCH] kdesu broken
> What is needed for a mistake free bisect is a 'doesn't matter as long
> as it matches' Makefile version that survives all the way through a
> bisect run.
I have a wrapper script I use for kernel builds that takes care of that
(it also supports cross building and building some out-of-tree modules).
Some snippets from that script below.
BISECTING=
if [ -e .git/BISECT_LOG ]; then
BISECTING=1
fi
[...]
if [ "$BISECTING" ]; then
# The version in the next line may need updating before a bisect
sed -i "s/^SUBLEVEL = .*/SUBLEVEL = 31/" Makefile
sed -i "s/^EXTRAVERSION =.*/EXTRAVERSION = -bisect/" Makefile
fi
[...]
make ...
[...]
if [ "$BISECTING" ]; then
# Revert Makefile to avoid errors on 'git bisect good/bad'
git checkout Makefile
fi
I use the deb-pkg target and also set the .deb package version in the
second hunk:
KERNELDEBREVISION=$(grep "^git[- ]bisect" .git/BISECT_LOG | wc -l)
This way I end up with a nice series of packages whose numbering matches
the steps in .git/BISECT_LOG:
linux-image-2.6.31-bisect_1_amd64.deb
linux-image-2.6.31-bisect_2_amd64.deb
linux-image-2.6.31-bisect_3_amd64.deb
...
Hope that help.
Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists