{"thread":{"id":"47896","subject":"Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order)","startedAt":"2018-02-21T23:28:43Z","lastAt":"2018-02-21T23:57:14Z","messageCount":2,"participants":["Josh Tepper"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"339861","messageId":"CAPFeJUA=7NyZZxkjpYjoRiXTb1WA1cQ-dYsn_XykMYt=iWGKOA@mail.gmail.com","threadId":"47896","inReplyTo":null,"subject":"Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order)","fromName":"Josh Tepper","fromEmail":"josh@clarifai.com","sentAt":"2018-02-21T23:28:18Z","receivedAt":"2018-02-21T23:28:43Z","isPatch":false,"sender":{"key":"josh@clarifai.com","avatar":null},"body":"When using git log, boundary commits (ie, those commits added by\nspecifying --boundary) do not respect the order (e.g., --date-order,\n--topo-order).  Consider the following commit history, where number\nindicates the order of the commit timestamps:\n\n<view with a fixed with font! 3's ancestor is 1, 6's ancestors are 4,5>\n0----1----2----5  <--A\n       \\         \\\n         3----4----6  <--B\n\n\nExecuting the following command:\n\n$ git log --boundary --date-order ^A B\n\nShould produce the following order (boundary commits shown with dashes):\n6 -5 4 3 -1\n\nHowever, it in fact produces:\n6 4 3 -7 -1\n\nPlease advise.\n\nBest,\n~Josh\n"},{"id":"339869","messageId":"CAPFeJUBZCZ2RxzZrF3Nd+rBBRhERpQV3ka6a6r+yMfk=gEg8gQ@mail.gmail.com","threadId":"47896","inReplyTo":"CAPFeJUA=7NyZZxkjpYjoRiXTb1WA1cQ-dYsn_XykMYt=iWGKOA@mail.gmail.com","subject":"Re: Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order)","fromName":"Josh Tepper","fromEmail":"josh@clarifai.com","sentAt":"2018-02-21T23:56:47Z","receivedAt":"2018-02-21T23:57:14Z","isPatch":false,"sender":{"key":"josh@clarifai.com","avatar":null},"body":"TYPO IN EXPECTED OUTPUT.\n\nTo avoid inevitable confusion, creating new thread \"Bug: git log:\nboundary commits do not respect order (e.g. date-order, topo-order)\n2\".\n\nDON'T REPLY TO THIS MESSAGE.  Instead reply to the new message\n\nOn Wed, Feb 21, 2018 at 6:28 PM, Josh Tepper <josh@clarifai.com> wrote:\n> When using git log, boundary commits (ie, those commits added by\n> specifying --boundary) do not respect the order (e.g., --date-order,\n> --topo-order).  Consider the following commit history, where number\n> indicates the order of the commit timestamps:\n>\n> <view with a fixed with font! 3's ancestor is 1, 6's ancestors are 4,5>\n> 0----1----2----5  <--A\n>        \\         \\\n>          3----4----6  <--B\n>\n>\n> Executing the following command:\n>\n> $ git log --boundary --date-order ^A B\n>\n> Should produce the following order (boundary commits shown with dashes):\n> 6 -5 4 3 -1\n>\n> However, it in fact produces:\n> 6 4 3 -7 -1\n>\n> Please advise.\n>\n> Best,\n> ~Josh\n"}]}