On Sat, 2014-07-19 at 09:15 +1000, Andrew Worsley wrote: > It looks innocent enough - but I have bisected it down to with (bad) > and just before (good)... > > 4c823cc3d568277aa6340d8df6981e34f4c4dee5 is the first bad commit [...] This commit only changes the loopback block driver and doesn't affect writing optical media in any way. Whatever the bug is, it probably only sometimes causes failure, which means some of the commits you thought were good were not. That will cause git bisect to blame a random later commit. Assuming that this regression only happened once, we can be fairly confident that it happened before 4c823cc3d568277aa6340d8df6981e34f4c4dee5, but as that is around v3.2-rc1 it doesn't reduce the range very much. :-( Ben. -- Ben Hutchings Make three consecutive correct guesses and you will be considered an expert.
Attachment:
signature.asc
Description: This is a digitally signed message part