{"thread":{"id":"56906","subject":"Ordering list of commits by topo-order","startedAt":"2021-11-15T15:00:30Z","lastAt":"2021-11-15T15:00:30Z","messageCount":1,"participants":["Íñigo Huguet"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"441137","messageId":"CACT4oufbbtCUjd1DcBcmUYhh_dmgsXxXLGSCrOstNxrwYEA4Sg@mail.gmail.com","threadId":"56906","inReplyTo":null,"subject":"Ordering list of commits by topo-order","fromName":"Íñigo Huguet","fromEmail":"ihuguet@redhat.com","sentAt":"2021-11-15T14:59:59Z","receivedAt":"2021-11-15T15:00:30Z","isPatch":false,"sender":{"key":"ihuguet@redhat.com","avatar":null},"body":"Hello, I have a list of hashes of commits which I want to order by\ntopological order. I'm trying this: `git rev-list --topo-order\n--no-walk <commit1> <commit2>`\n\nHowever, no matter what I do, I always get the 2 commits in the order\nI provide them in the input.\n\nAs an example, I'm using commits from Linux kernel `e4073430ee1de` and\n`0d55b76fd815f4`:\n\n$ git log --topo-order -2 --oneline 0d55b76fd815f4\n0d55b76fd815 ath11k: setup REO for WCN6855\ne4073430ee1d ath11k: add dp support for WCN6855\n\n$ git rev-list --topo-order --no-walk 0d55b76fd815f4 e4073430ee1de\n0d55b76fd815f4d685a62afe44e623501186ceb4\ne4073430ee1dec5402a6158755ac8b84eade83c6\n\n$ git rev-list --topo-order --no-walk e4073430ee1de 0d55b76fd815f4\ne4073430ee1dec5402a6158755ac8b84eade83c6\n0d55b76fd815f4d685a62afe44e623501186ceb4\n\n$ git rev-list --topo-order --no-walk=sorted e4073430ee1de 0d55b76fd815f4\ne4073430ee1dec5402a6158755ac8b84eade83c6\n0d55b76fd815f4d685a62afe44e623501186ceb4\n\nIs it possible to obtain a fixed list of commits sorted by topological order?\n-- \nÍñigo Huguet\n\n"}]}