On Sun, Nov 16, 2008 at 01:44, Ian Hilt <ian.hilt@xxxxxxx> wrote: > Why is it that this command, > > git rev-list --reverse --max-count=1 <branch> > > results in the same SHA1 as, > > git rev-list --max-count=1 <branch> > > So far, the documentation and the mailing list archives haven't helped. The --reverse is applied after the --max-count, so you are seeing the reverse of one commit ;). For comparison, have a look at: $ git rev-list --reverse --max-count=2 -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html