Dependency output order bad ...

So my dep list is about 180 commits ... so I extracted the column 2 list, reversed the order and used the result to form a git cherry-pick command. The first commit in the resulting command failed because of conflicts. Digging and digging I figured out that the dependency order doesn't work. The dependency is written to stdout when first encountered. If a subsequent commit also depends on it, it needs to be applied before that 2nd commit.

I'm not sure yet how to achieve that, partly because my git expertise is minimal. Essentially, the deepest dependency would seem like the right output order.

Start by tracing how the dependency list is written to stdout, then reproduce the reported workflow by reversing the column-two output into a git cherry-pick command. Done means the output places deeper dependencies before commits that depend on them, so the listed commits can be applied without the reported ordering conflicts.

Written by the indexing model from the issue text.