On Mon, 31 Oct 2005, Junio C Hamano wrote:
David Lang <[email protected]> writes:
given the time required to compile a kernel and reboot you can't plan to
keep the info server side (browser connections will time out well before
this finishes)
instead this will require saving something on the client and passing it
back to the server.
I was thinking about doing thatn in hidden input fields and
passing form back and forth. After all what real git bisect
keeps locally are one bad commit ID and bunch of good commit
IDs.
if it's kept in a file or cookie then it can survive a reboot and other
distractions (remember that this process can take days if the problem
doesn't show up at boot). a cookie can hold a couple K worth of data, a
file has no size limit.
it would also be a good idea if the web page could give an estimate
estimate of how many additional tests may end up being required.
David Lang
--
There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.
-- C.A.R. Hoare
-
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]
