![]() | |||||||||||||
Messages in this thread |
--- Pekka Enberg <penberg@cs.helsinki.fi> wrote: > On 3/16/07, Greg KH <gregkh@suse.de> wrote: > > Is there any way you can use 'git bisect' to try to track down the root > > cause of this? > Chris, If 2.6.19 works for you, could you please do a git bisect for > this bug? See the following URL for details: > > http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt That would take ages - the only reason I kept on plugging away with winecfg last night was because I was fairly certain the kernel was going to "oops" eventually (which it did). But when exactly would I be able to declare a kernel "good" during a "git bisect"? Cheers, Chris ___________________________________________________________ What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship. http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-03-16 09:35 [from the cache] ©2003-2008 | |||||||||||||