![]() | |||||||||||||
Messages in this thread |
On Fri, 18 Nov 2005 17:18:40 -0800 Greg KH wrote: > Is there any way you could be able to run 'git bisect' between 2.6.12 > and 2.6.13 to try to find the offending changeset? I would really > appreciate it. I'll take one beer (or in .ru: \u043f\u0438\u0432\u043e) for each hour ;-) This is a six-pack: 299de0343c7d18448a69c635378342e9214b14af is first bad commit diff-tree 299de0343c7d18448a69c635378342e9214b14af (from 90b54929b626c80056262d9d99b3f48522e404d0) Marvellous tool, that git. But it took less time - for us users - when we only had to wave in a general -rc direction... I've not tried to back the commit out from a 2.6.14 kernel, though. Will wait for a real fix. Mvh Mats Johannesson -- - 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: 2005-11-19 13:08 [from the cache] ©2003-2008 | |||||||||||||