> 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? -- Markus --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
