Comment #16 on issue 3992 by [email protected]: Using dodecaphonic and
dodecaphonic-no-repeat there is no difference
http://code.google.com/p/lilypond/issues/detail?id=3992
Well, I did not partake in reviewing issue 2068 which is responsible for
those instructions.
To be fair: those instructions strongly suggest using gitk before the final
push, implying to abort if you find the result unsatisfactory.
Excellent advice. Most of the other instructions are not best practice.
At any rate: there is no way _now_ that would make the history less
contorted. I'll have to rewrite that section. I think it must be sort of
duplicate since I am rather sure that we have carved out better procedures
as well and _hopefully_ included them _somewhere_.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
