Hi, Andrew Morton wrote:
> - If you hit a bug in -mm and it's not obvious which patch caused it, it
> is
> most valuable if you can perform a bisection search to identify which
> patch introduced the bug. Instructions for this process are at
>
> http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
You can also use the mm->git tree (at .../linux/kernel/git/smurf/
/linux-trees.git) and use "git bisect".
It'll be a bit slower, but the upside is that it's able to descend into
the git trees which Andrew has imported into mm as monolithic patches.
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [email protected]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
I do not fear computers. I fear the lack of them.
-- Isaac Asimov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
