Francisco Vila <paconet....@gmail.com> writes: > On the other hand, I can not omit doing things forever just for > safety. Therefore, I have to assume a certain degree of risk. I > already apologized when it went bad. After that, everything has gone > smoothly. Git history will judge us all.
The thing to remember is that git history can be both _viewed_ and _changed_ before pushing it upstream. So there is not much of a risk one has to assume. Graham asked for extra carefulness when pushing directly to release/unstable. That is different from asking for extra fatalism because one can always check what one is doing. The current spacing folderol in connection with issue 2468 makes this a moot point right now: we can't really release 2.15.37 as 2.16, so translators have a bit more time for business as usual. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
