* how to use git bisect on such seanario
@ 2012-12-24 2:35 bill4carson
2012-12-24 2:57 ` Subramaniam Appadodharana
0 siblings, 1 reply; 3+ messages in thread
From: bill4carson @ 2012-12-24 2:35 UTC (permalink / raw)
To: kernelnewbies
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* how to use git bisect on such seanario
2012-12-24 2:35 how to use git bisect on such seanario bill4carson
@ 2012-12-24 2:57 ` Subramaniam Appadodharana
2012-12-24 3:03 ` bill4carson
0 siblings, 1 reply; 3+ messages in thread
From: Subramaniam Appadodharana @ 2012-12-24 2:57 UTC (permalink / raw)
To: kernelnewbies
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 at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20121223/da78e980/attachment.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* how to use git bisect on such seanario
2012-12-24 2:57 ` Subramaniam Appadodharana
@ 2012-12-24 3:03 ` bill4carson
0 siblings, 0 replies; 3+ messages in thread
From: bill4carson @ 2012-12-24 3:03 UTC (permalink / raw)
To: kernelnewbies
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 <bill4carson at gmail.com <mailto: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 at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
--
?????????
--bill
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-12-24 3:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-24 2:35 how to use git bisect on such seanario bill4carson
2012-12-24 2:57 ` Subramaniam Appadodharana
2012-12-24 3:03 ` bill4carson
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).