On 7/08/09 22:24, Markus wrote: > >> To be sure of what introduced the behavior change and fix it, I suggest >> you git bisect the case, provided you have an integration test (you can >> even run an automated git bisect). > > I tried this a bit ago and when I came back to see what had happened > (I'm multitasking), I realized that it was only bisecting back to when I > cloned the repo (e.g. local history). The git bisect start had warned > me but I blew past it (doh!). Anybody know how to bisect through > commits prior to your first clone?
It was my understanding that cloning preserve the whole history from day one, except if you use some git magic tricks. So my usual git bisect workflow is: % git bisect start % git bisect bad <commit I know is bad, usually HEAD> % git bisect good <commit I know is good for sure, for instance 0.25beta2> % run the test case, then mark bad or good, wash and rinse one more time until the culprit is found. This last step can be fully automated and you can do other thing useful meanwhile :-) -- Brice Figureau My Blog: http://www.masterzen.fr/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
