On Thu, Oct 09, 2014 at 08:38:09AM +0000, Thorsten Glaser wrote: > Andreas Henriksson dixit: > > >Since you seem to have a way to reproduce the problem, could you please > >also git bisect it? > > Not this week ☹ also, never worked with that before, I’d have to > learn it first. Unless it can be automated? If the result of script > contains “Total passed”, it worked, otherwise not.
git bisect is a way to automate manual tasks, so I'm not sure how to make it more automated (or what you question really is). See 'man git bisect' or http://git-scm.com/docs/git-bisect basically: git bisect start v2.25.1 v2.20.1 -- term-utils/script.c ./autogen.sh && ./configure && make <reproduce using ./script (instead of /usr/bin/script)> git bisect <bad|good> <rinse and repeat step 2+3 until git tells you the bad commit> Regards, Andreas Henriksson PS. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764580 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
