thanks, I know what you mean, let the good be "bad",and the bad be "good"。。。。
On 2012年12月24日 10:57, Subramaniam Appadodharana wrote: > 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 <bill4car...@gmail.com > <mailto:bill4car...@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 <mailto:Kernelnewbies@kernelnewbies.org> > > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -- 浮沉随浪只记今朝笑 --bill _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
