Along with tagging+releasing, wouldn't be great to know which commit does a release come from, just making the build process to write it down in a README file? Nowadays, tagging is a manual event that can be forgotten (and it is).
Also, it would be useful to know what commit has a webpage been produced from, by inserting it as an HTML comment. But, as all these comments would be identical, only one is necessary, given that it is in at lease ONE page whose raw code one can examine. For example, how old are Reinhold's docs? It is difficult to say from Version 2.13.0 05MAR09 This page is for LilyPond-2.13.2 > On Sat, Jun 6, 2009 at 5:57 PM, Graham Percival<gra...@percival-music.ca> > wrote: >> Does anybody remember which commit was used for 2.13.1? We should >> tag that. >> >> Cheers, >> - Graham -- Francisco Vila. Badajoz (Spain) www.paconet.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
