• Show log

    Commit

  • Hash : 3cabf8d1
    Author : Carlos Martín Nieto
    Date : 2018-09-17T14:39:58

    revwalk: use the max value for a signed integer
    
    When porting, we overlooked that the difference between git's and our's time
    representation and copied their way of getting the max value.
    
    Unfortunately git was using unsigned integers, so `~0ll` does correspond to
    their max value, whereas for us it corresponds to `-1`. This means that we
    always consider the last date to be smaller than the current commit's and always
    think commits are interesting.
    
    Change the initial value to the macro that gives us the maximum value on each
    platform so we can accurately consider commits interesting or not.
    
    (cherry picked from commit 46f35127b6fcfab87cb80d1b772ac7c662eafd38)