Neil Puttock n.putt...@gmail.com writes:
On 20 September 2011 21:50, Benkő Pál benko@gmail.com wrote:
I don't know what to do, could you help me?
The attached patch works for me (haven't run make check on it though).
I have taken the liberty of pushing it after looking it through (I
Neil, David,
I don't know what to do, could you help me?
The attached patch works for me (haven't run make check on it though).
I have taken the liberty of pushing it after looking it through
thanks to both of you: the patch works and I've learnt something
about LilyPond again.
p
hi David,
LilyPond barfs at
\book
{
\bookOutputName foo
{ a' }
}
git bisect gave me commit
24fdf0d37cec73564162324ab74ed5e3a6824e8c
to blame.
I don't know what to do, could you help me?
p
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 20 September 2011 21:50, Benkő Pál benko@gmail.com wrote:
I don't know what to do, could you help me?
The attached patch works for me (haven't run make check on it though).
Cheers,
Neil
From f6f1ad62263b4dfb5f518da71891d3a0b30c89a3 Mon Sep 17 00:00:00 2001
From: Neil Puttock
Benkő Pál benko@gmail.com writes:
hi David,
LilyPond barfs at
\book
{
\bookOutputName foo
{ a' }
}
git bisect gave me commit
24fdf0d37cec73564162324ab74ed5e3a6824e8c
to blame.
I don't know what to do, could you help me?
The easiest thing to do is to revert the patch.
Neil Puttock n.putt...@gmail.com writes:
On 20 September 2011 21:50, Benkő Pál benko@gmail.com wrote:
I don't know what to do, could you help me?
The attached patch works for me (haven't run make check on it though).
That would pretty much be what I would consider a proper fix and
