It should work the same way as for finding a bug. Only the "bad" commit would simply be the one to solve the bug <br><br>On Sunday, December 23, 2012, bill4carson <<a href="mailto:bill4carson@gmail.com">bill4carson@gmail.com</a>> wrote:<br>
> Hi, list<br>><br>> Usually, we use git bisect to identify which commit causes trouble,<br>><br>> while how do I do when need to find out which commit solve problem?<br>> for example, it's know there is an bug since commit A, but I find out<br>
> the newest version (commit B)is good, so one commit between commit A and<br>> B solve the problem,<br>><br>><br>> thanks<br>><br>> --<br>> ¸¡³ÁËæÀËÖ»¼Ç½ñ³¯Ð¦<br>><br>> --bill<br>><br>> _______________________________________________<br>
> Kernelnewbies mailing list<br>> <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
>