Hi, when I've seen the inclusion of git information on lilypondblog [1], I liked it and adapted it to my taste:
Of course one can include a whole git log in the score, but the only thing I was interested in is this: If I have a printed score or a PDF, I want to know which version that was. All the rest I can look up in git. And the versioning, I do with tags because I like it more than hexadecimal hashes. I have a tag for each year and each commit since then is counted, so what I write on the score looks like: Version 2018.25 It's derived from `git describe`, the full command is: git describe --long --dirty='+' | sed 's/-/./' | sed -r 's/-g[0-9a-f]+//g' I like the combination of `git describe` and tags a lot. That's my personal optimum between usefulness and beauty for both technical and non-technical readers of the score. Cheers, Joram [1]: http://lilypondblog.org/2014/04/printing-git-versioning-info-in-a-score/ _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
