Dec. 24, 2012
2:57 a.m.
It should work the same way as for finding a bug. Only the "bad" commit would simply be the one to solve the bug On Sunday, December 23, 2012, bill4carson <bill4carson@gmail.com> wrote:
Hi, list
Usually, we use git bisect to identify which commit causes trouble,
while how do I do when need to find out which commit solve problem? for example, it's know there is an bug since commit A, but I find out the newest version (commit B)is good, so one commit between commit A and B solve the problem,
thanks
-- 浮沉随浪只记今朝笑
--bill
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies