Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #12 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #11 by joeneeman:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_38
--
You received this message because you ar
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #10 by v.villenave:
Anyway, I have reverted all my commits as soon as I read Graham's
answer... So if
anyone wants to push Joe's patches, I leave it up to you now :)
However, thank
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #9 by joeneeman:
It was partly for review and partly that I am just unable to push them myself,
lacking an internet-facing computer with git installed. I have done all
the standard
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #8 by v.villenave:
Oh, I'm sorry. I was afraid it could be inappropriate, but it was just
too tempting
to see Joe's patches! (Besides, I typed 2_11_28 instead of 2_11_28.)
OK, back
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #7 by gpermus:
This isn't fixed; Joe was asking Han-Wen to examine the patches to see
if they were
acceptable.
Valentin: in general, don't change the status to "fixed" or
add "fix
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #6 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Labels: fixed_2_11_28
--
You received this message because you are listed in the owner
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #5 by v.villenave:
Thank you very much Joe.
Maybe I was the one supposed to apply your patches (hope I did nothing
wrong though).
If I was not, or if I did wrong, please apologize.
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #4 by joeneeman:
Here is a set of patches; number 5 fixes this bug and it should apply separately
from the others. I´ve attached others here too because I don´t know
when I will next
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #3 by joeneeman:
(No comment was entered for this change.)
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC f
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #2 by joeneeman:
I have a fix on my laptop but no internet access. If I find an internet
cafe that
allows USB sticks, I´ll format a patch and mail it to you.
--
You received this m
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
Comment #1 by hanwenn:
Joe,
Can you have a look? The cluster code does not trigger vertical
positioning of the
staves.
Issue attribute updates:
Cc: joeneeman
--
You received thi
Issue 533: input/regression/cluster-cross-staff.ly
http://code.google.com/p/lilypond/issues/detail?id=533
New issue report by gpermus:
Clusters can be written across staves" but the cluster remains in
the lower stave only, despite the \change Staff = up tag. Taking
notes up an octave only increas
13 matches
Mail list logo
