From mboxrd@z Thu Jan 1 00:00:00 1970 From: bill4carson@gmail.com (bill4carson) Date: Mon, 24 Dec 2012 11:03:39 +0800 Subject: how to use git bisect on such seanario In-Reply-To: References: <50D7BF81.6000102@gmail.com> Message-ID: <50D7C60B.50907@gmail.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org 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 > 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 at kernelnewbies.org > > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > -- ????????? --bill