On Wed, Aug 31, 2016 at 1:41 PM, Ben North <ben@xxxxxxxxxxxxxxxx> wrote: > > https://github.com/bennorth/git-dendrify So looking at the Readme there: * Add printing facility |\ | * Add watermarks | |\ | | * Allow choice of colour | | * Add known-good test cases | | * Emit watermark 'underneath' main output | | * Drop-down for common watermarks | |/ | * Add actual printing via PDF | |\ | | * Submit PDF to system print service ... This reminds me of the workflow of git itself. (As a literate consumer) You get an easy top-level overview what the community is interested in via e.g.: git log --first-parent --oneline That would be equivalent to showing only * Add printing facility If you run that command on "* Add printing facility"^2 you would see the headlines of the section. However in gits reality we do not have these nice sections building on top of each other, as many people are interested in different things and build where they see fit. > The hierarchical organisation is helpful when reading the > history, and also allows that history to be rendered into a structured > document explaining the code's development. How does the linearify/dendrify work with already non-linear history? Thanks, Stefan