On Wed, Jan 25, 2012 at 09:20:18PM +0100, David Kastrup wrote: > WTF? That's definitely something in the changes file. I checked this > and it compiled and I had code that made sure it compiled. With all the > rebasing to make this fit better I must have displaced the relevant > commit that explicitly makes this compile somehow after all. I'll be > pushing that ASAP and check the translations afterwards.
I see your fix. However, I'm reluctant to run patchy-staging right now, since it would leave master broken in 1f0a00b69403290b7fc7527b9ab100f95533f954 and fixed in 75d0e8cf509685df2e0ed5722803622258673c07 True, we're unlikely to have git-bisect stop in between those two commits, but would it be possible for you to include the parser.yy fix in the relevant branch merge so that there isn't any danger when running git-bisect? - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
