On Tue, Nov 13, 2007 at 12:50:08PM -0500, Mark Lord wrote:
It's also godsend for users who want a regression they observe fixed.
If you can tell which patch broke it you often turned a very hard to
debug problem into a relatively easy fixable problem.
As an example, [1] was an issue a normal user could discover, and
bisecting made the difference between "nearly undebuggable" and
"easily fixable by revertng a commit".
As already said in thread, the required instructions for bisecting are
relatively short and simple (assuming the user can build his own
kernels).
Not everyone has a slow connection.
For me, the speed of cloning a tree from git.kernel.org is completely
cpu bound and limited by the speed of the 1.8 Ghz Athlon in my
computer...
But if there is a real life problem like people with extremely slow and
expensive internet connections not being able to bisect bugs these
problems should be named and fixed (e.g. by sending CDs).
cu
Adrian
[1] http://lkml.org/lkml/2007/11/12/154
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
