How does "git log" determine commit order when displaying history, and what is the difference between "--topo-order" and the default chronological ordering when branches have merge commits?
Correct! Well done.
Incorrect.
The correct answer is A) By default, "git log" generally orders commits by date, which can interleave commits from different branches by timestamp; "--topo-order" ensures no commit shows before its descendants, so a feature branch's commits appear together before its merge commit
Correct Answer
By default, "git log" generally orders commits by date, which can interleave commits from different branches by timestamp; "--topo-order" ensures no commit shows before its descendants, so a feature branch's commits appear together before its merge commit
This distinction matters when timestamps don't reflect the logical order of integration — e.g. if a long-lived branch with old commit dates is merged later, default date-based ordering might interleave its commits confusingly among more recent ones, whereas "--topo-order" keeps the graph structure coherent.