> On Sun, Mar 08, 2015 at 05:24:53PM +0100, Markus Teich wrote:
>Roger wrote:
>> Whomever coded these early versions, might be able to very easily locate the
>> slowdown explicitly at this point.
>
>Heyho Roger,
>
>just use `git bisect` to locate the commit responsible for the slowdown.
I've heard or known about 'git bisect' for the longest time, but do not have
infinite amounts of time for always learning new tools. ;-)
Until I git to learning bisect, I got done what I needed to git done using the
old fashion method!
--
Roger
http://rogerx.freeshell.org/
Received on Sun Mar 08 2015 - 17:31:06 CET