Hi<br><br>On Sunday, October 12, 2014, Neil Salstrom <<a href="mailto:salstrom@gmail.com">salstrom@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><br></div><div>This time I ran the bisect between 6788ea9 (good, August 8) and 082d5c1 (bad, August 10). The bisect ended with:<br><br>commit f307a3d5e60b0054e1833127d417c6acfada3213<br>Author: Lawrence Rust <<a href="javascript:_e(%7B%7D,'cvml','lvr@softsystem.co.uk');" target="_blank">lvr@softsystem.co.uk</a>><br>Date: Thu Jun 2 12:55:13 2011 +0200<br><br> Player: Improve low bit rate / high latency stream playback <br><br></div><div>Which clearly shows I'm clueless on how bisect works as I tried to do it between the commits on the 8th and 10th. Again I had one bisect trial that </div><div></div></div></div></div></blockquote><div><br></div><div>Because the date of when a change was made is not necessarily the date a change was committed to the main tree. </div><div><br></div><div>It was written in June 2011, but only backported in August. </div><div><br></div><div>Can you just revert the commit that is marked as "bad"?</div><div><br></div><div>Or more easily. What about going backward further and see if that still works. In particular before any of Lawrence Rust commits were ever pushed. </div><div><br></div><div>Most of them appear to have caused strong regression unfortunately. </div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div></div></div></div>
</blockquote>