aspiers/git-deps

Dependency output order bad ...

Open

#62 aberto em 12 de out. de 2016

Ver no GitHub
 (10 comments) (0 reactions) (0 assignees)Python (55 forks)github user discovery
enhancementhelp wanted

Métricas do repositório

Stars
 (318 stars)
Métricas de merge de PR
 (Métricas PR pendentes)

Description

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.

Guia do colaborador