aspiers/git-deps

Dependency output order bad ...

Open

#62 aperta il 12 ott 2016

Vedi su GitHub
 (10 commenti) (0 reazioni) (0 assegnatari)Python (55 fork)github user discovery
enhancementhelp wanted

Metriche repository

Star
 (318 star)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

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.

Guida contributor