TYPO IN EXPECTED OUTPUT. To avoid inevitable confusion, creating new thread "Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order) 2".
DON'T REPLY TO THIS MESSAGE. Instead reply to the new message On Wed, Feb 21, 2018 at 6:28 PM, Josh Tepper <j...@clarifai.com> wrote: > When using git log, boundary commits (ie, those commits added by > specifying --boundary) do not respect the order (e.g., --date-order, > --topo-order). Consider the following commit history, where number > indicates the order of the commit timestamps: > > <view with a fixed with font! 3's ancestor is 1, 6's ancestors are 4,5> > 0----1----2----5 <--A > \ \ > 3----4----6 <--B > > > Executing the following command: > > $ git log --boundary --date-order ^A B > > Should produce the following order (boundary commits shown with dashes): > 6 -5 4 3 -1 > > However, it in fact produces: > 6 4 3 -7 -1 > > Please advise. > > Best, > ~Josh
