Graham Percival <[email protected]> writes: > On Tue, Feb 21, 2012 at 08:49:21PM +0100, David Kastrup wrote: >> Uh, Graham? Just fixed another regression discovered by an LSR failure >> and pushed to staging. It would appear that this needs to be in 2.16 >> according to our policies. > > Well, there's already 2 Critical issues, and I think that 2335 > should qualify as well but I don't feel like arguing at the > moment. So no worries about having 2.16 happen unexpectedly.
I just bungled staging with bad Texinfo in a regtest and saw that you merged into it right after that, presumably because of a release. I can either replace the merge (it will no longer have the same commit id) or throw it out altogether. What should it be? Sorry for that. -- David Kastrup _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
