[Freeswitch-users] Hunting down bugs with git bisect

Tue Apr 23 07:44:15 MSD 2013

Collins, contact me on irc tomorrow and I'll give you the scripts I have.

William King
Senior Engineer
Quentus Technologies, INC
1037 NE 65th St Suite 273
Seattle, WA 98115
Main:   (877) 211-9337
Office: (206) 388-4772
Cell:   (253) 686-5518
william.king at quentustech.com

On 04/19/2013 04:58 PM, Michael Collins wrote:
> Hello gang!
> 
> I'm soliciting feedback on this topic: using git bisect to find "the
> commit that broke it." I am particularly interested in anyone who has
> automated the process so that it will build, test, pull, build, test,
> pull, etc. automatically without human intervention.
> 
> If you've done anything like that please let us know. I'd like to see
> git bisect used more for people who are reporting bugs with phrases
> like, "It stopped working when I updated so I went back to the old git
> version and it works fine there."
> 
> Thanks!
> 
> -- 
> Michael S Collins
> Twitter: @mercutioviz
> http://www.FreeSWITCH.org
> http://www.ClueCon.com
> http://www.OSTAG.org
> 
> 
> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org