Using git log / rev-list internal pagination

We are planning to execute git rev-list command with “–skip” and “–max-count” arguments using ScmCommandBuilder. I noticed that current implementation of method com.atlassian.stash.internal.scm.git.DefaultGitCommandFactory#commits(com.atlassian.bitbucket.repository.Repository, com.atlassian.bitbucket.scm.CommitsCommandParameters, com.atlassian.bitbucket.util.PageRequest) doesn’t rely on these arguments, so com.atlassian.stash.internal.scm.git.command.revlist.PagedCommitRevListOutputHandler reads all commits and then skips commits before start position of PageRequest.
Is there any reason why you are not using “–skip” and “–max-count”?