• Tom Lane's avatar
    Fix some more bugs in git_changelog. · 30d2e100
    Tom Lane authored
    1. Don't forget the last (oldest) commit on the oldest branch.
    
    2. When considering which commit to print next, if two alternatives have
    the same "distortion" score (which is actually the normal case, since
    generally the "distortion" is 0), then choose the later timestamp to
    print first.  I don't know where Robert got the idea to ignore timestamps
    and sort by branch age, but it wasn't a good idea: the resulting ordering
    of commits was just plain bizarre anywhere that some branches had many
    fewer commits than others, which is the typical situation for us.
    30d2e100
git_changelog 4.65 KB