Re: Literate programming with git

Hi Stefan, Thanks for the remarks. >> https://github.com/bennorth/git-dendrify > > [...] 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 > >

Re: Literate programming with git

> How does the linearify/dendrify work with already non-linear history? The current implementation using magic strings in commit messages seems incompatible with existing projects. How about annotating an existing project with git-notes instead? You could add notes to existing commits without nee

Re: Literate programming with git

On Wed, Aug 31, 2016 at 1:41 PM, Ben North 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 'und

Literate programming with git

Hi, I've recently been experimenting with using git to make software more human-readable. Presenting software for humans to read is not a new idea (Knuth's 'literate programming'), but I think git can be a new tool for showing the development of code in a structured way. Merge-commits can break a