From: Rob Landley <rob@landley.net>
To: David Lang <david.lang@digitalinsight.com>
Cc: Junio C Hamano <junkio@cox.net>, linux-kernel@vger.kernel.org
Subject: Re: [git patches] 2.6.x libata updates
Date: Mon, 31 Oct 2005 03:34:34 -0600 [thread overview]
Message-ID: <200510310334.35597.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0510310109250.16065@qynat.qvtvafvgr.pbz>
On Monday 31 October 2005 03:13, David Lang wrote:
> > 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.
Actually, lots of Linux browsers these days treats all cookies as session
cookies for security reasons. So surviving a reboot still isn't guaranteed.
But it's possible.
You can also have 'em bookmark a URL...
> 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.
Bisect already says how many commits are left in the pool, so roughly log(2)
of that...
> David Lang
Rob
next prev parent reply other threads:[~2005-10-31 9:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-29 18:22 [git patches] 2.6.x libata updates Jeff Garzik
2005-10-29 19:14 ` Andrew Morton
2005-10-29 19:20 ` Jeff Garzik
2005-10-29 19:37 ` Linus Torvalds
2005-10-29 20:09 ` Al Viro
2005-10-29 20:16 ` Jeff Garzik
2005-10-29 20:18 ` Nicolas Pitre
2005-10-29 21:01 ` Linus Torvalds
2005-10-30 15:46 ` Nicolas Pitre
2005-10-29 22:21 ` Andrew Morton
2005-10-29 22:30 ` Linus Torvalds
2005-10-30 0:55 ` Tony Luck
2005-10-30 2:28 ` Horst von Brand
2005-10-30 12:44 ` Rob Landley
2005-10-30 22:36 ` Linus Torvalds
2005-10-30 23:31 ` Rob Landley
2005-10-31 0:58 ` Linus Torvalds
2005-10-31 2:35 ` Rob Landley
2005-10-31 7:46 ` Junio C Hamano
2005-10-31 8:10 ` David Lang
2005-10-31 8:28 ` David Lang
2005-10-31 9:00 ` Junio C Hamano
2005-10-31 9:13 ` David Lang
2005-10-31 9:34 ` Rob Landley [this message]
2005-10-31 11:45 ` Giuseppe Bilotta
2005-10-31 17:49 ` David Lang
2005-10-31 18:06 ` Giuseppe Bilotta
2005-10-31 2:52 ` Rob Landley
2005-11-10 0:36 ` Matthias Urlichs
2005-10-30 23:59 ` Rob Landley
2005-10-31 0:16 ` Randy.Dunlap
2005-10-30 13:11 ` Pavel Machek
2005-10-31 3:55 ` David Lang
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 2:15 Jeff Garzik
2006-01-18 2:33 ` Andrew Morton
2006-01-18 5:18 ` Jeff Garzik
2006-01-03 16:43 Jeff Garzik
2006-01-03 16:51 ` Bartlomiej Zolnierkiewicz
2006-01-03 16:56 ` Jeff Garzik
2006-01-03 17:32 ` Alan Cox
2006-01-03 17:43 ` Jeff Garzik
2006-01-03 18:35 ` Bartlomiej Zolnierkiewicz
2006-01-03 18:50 ` Alan Cox
2006-01-04 14:02 ` Alan Cox
2006-01-04 20:35 ` Matt Darcy
2006-01-04 22:25 ` Matt Darcy
2006-01-05 18:44 ` Terrence Martin
2006-01-05 20:29 ` Roman Gischig
2005-11-11 16:23 Jeff Garzik
2005-11-09 6:54 Jeff Garzik
2005-10-28 0:49 Jeff Garzik
2005-10-28 16:08 ` Linus Torvalds
2005-08-29 0:25 Jeff Garzik
2005-06-28 16:59 Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510310334.35597.rob@landley.net \
--to=rob@landley.net \
--cc=david.lang@digitalinsight.com \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.