CommitFilter / CommitSortStrategies Understanding

Issueで参照されているエントリポイント CommitFilter、CommitSortStrategies、QueryBy から始め、その後、それらの動作を記載されている git コマンドの例と比較してください。提案されている各同等性が正しいかどうかを文書化し、CommitSortStrategies.None の順序付けのセマンティクスを明記してください。質問について信頼できる説明が示されれば完了です。

I am trying to understand what "CommitSortStrategies" is actually doing to the commit collections that I am getting back and am just looking for clarification if this is correct.

Git, by default (cmd line app), are shown in reverse chronological order, so:

• git (default sort) == CommitFilter/SortBy of (Undefined)
• git --reverse != CommitFilter/SortBy of Reverse
• git --reverse == CommitFilter/SortBy of Reverse | Time
• git --topo-order == CommitFilter/SortBy of Topological
• git --reverse --topo-order == CommitFilter/SortBy of Reverse | Topological
• git --______ ?= CommitFilter/SortBy of None
• CommitFilter/SortBy of None != CommitFilter/SortBy of (Undefined)

Is that list correct/complete?

(FYI: I have a multi-million object repo with millions of refs and have reverted to shelling to git to get the commit lists between cross-merge branches as I can not get a direct match between libgit2's ls-trees and gits, my head hurts....)

BTW: What order does CommitSortStrategies.None follow? Based on ref creation order on the file-system, maybe?

A sample for a future reader:

# Note: Piping to head as you can not use -n <number>, --max-count=<number> as that is applied before commit ordering
git log HEAD..master --format="%ci %h %s" --reverse | head -10

So based upon the equivalence list above, in libgit2sharp this becomes:

var filter = new CommitFilter {
    SortBy = CommitSortStrategies.Reverse | CommitSortStrategies.Time,
    Since = master,  // determined by a prior repo.Lookup<Tree>
    Until = head, // determined by a prior repo.Lookup<Tree>                    
};
repo.Commits.QueryBy(filter).Take(10);