aspiers/git-deps

Dependency output order bad ...

Open

#62 建立於 2016年10月12日

在 GitHub 查看
 (10 留言) (0 反應) (0 負責人)Python (55 fork)github user discovery
enhancementhelp wanted

倉庫指標

Star
 (318 star)
PR 合併指標
 (PR 指標待抓取)

描述

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.

貢獻者指南