This looks normal. The order of the 'git rebase' plan shows the sequence in which commits will be applied from top to bottom.
You are probably thinking of 'git log', which uses the reverse order with the newest commit at the top.
You are probably thinking of 'git log', which uses the reverse order with the newest commit at the top.
Not sure why I was convinced otherwise, must be log's behaviour as you say. Had to test to believe it!