Thanks for the remarks.
> [...] 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.
That's a nice observation on how to use the existing git tools to view a
structured history with different levels of detail.
> 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.
Yes, reality isn't always clean! But each individual contributor can
structure their own branch in a hierarchical way if they think it would
be helpful, before publishing it for review.
> How does the linearify/dendrify work with already non-linear history?
If you attempt to 'linearize' a section of history which isn't of the
required hierarchical form, the tool exits without doing anything.
(Because this is only at the experimenting stage, there may well be
situations where it fails to detect an unexpected structure, but see
also next paragraph.) Similarly, if you attempt to 'dendrify' a section
of history which isn't purely linear, it refuses.
In any case, the tool only ever creates a new branch so your original
history is unaltered.