On Mittwoch, 27. Januar 2010, Michael Spang wrote:
Using --max-count with --reverse currently outputs the last N commits
in the final output rather than the first N commits. We want to
truncate the reversed list after the first few commits, rather than
truncating the initial list and reversing that.
So when you have this history (A is oldest, D is newest):
A--B--C--D
and you say
git log --max-count=2 --reverse D
then you want
A
B
but I want
C
D
Why is your interpretation correct, an mine wrong?
-- Hannes