-not show the branches in dependent order. While this project only expresses
-a single dependency per branch TopGit implements dependencies as a DAC just
-like Git. To see the dependencies you will need to use the --graphviz
-option and pipe the result to dot for display. The following command while
-long works fairly well for me. Longer term it would be nice to update this
-option to use a preferred config options stored in the repo if they exist.
-
- > tg summary --graphviz | dot -Txlib -Nfontsize=8 -Eminlen=0.01 \
- -Grankdir=LR -Nheight=0.3 -Nwidth=2 -Nfixedsize=true
+not show the branches in dependent order. This is done because TopGit allows
+each branch to express multiple dependencies as a DAC. Initially this seemed
+like an added complication which I planned to avoid by just implementing a
+stack using the graph. However, this ended up being problematic because
+with a stack when a change was made to a branch near the base, it was a
+very expensive operation to merge the change up to the top of the stack.
+By defining the dependencies as a graph it is possible to keep the depth
+much shallower thus minimizing the merging. It has also proved insightful
+as to each patches actual dependencies.
+
+To see the dependencies you will need to use the --graphviz option and pipe
+the result to dot for display. The following command works fairly well for
+me. Longer term it would be nice to update this option to use a preferred
+config options stored in the repo.
+
+ > tg summary --graphviz | dot -Txlib -Nfontsize=8