Updates:
Status: Verified
Comment #5 on issue 1888 by brownian.box: Introduce a maximum depth for
markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Labels: -Patch-review
Comment #4 on issue 1888 by n.putt...@gmail.com: Introduce a maximum depth
for markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
(No comment was entered for this change.)
___
bug-lilyp
Comment #3 on issue 1888 by brownian.box: Introduce a maximum depth for
markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
Why Patch-review? Please, remove it first.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https:/
Updates:
Status: Fixed
Labels: fixed_2_15_12
Comment #2 on issue 1888 by reinhold...@gmail.com: Introduce a maximum
depth for markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
Pushed as 16e626a8524421eda692cb19be6d0ec5bff723b7
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1888 by pkx1...@gmail.com: Introduce a maximum depth
for markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
passes make and reg tests (with other patch applied first and this one on
top)
_
Status: Accepted
Owner: reinhold...@gmail.com
Labels: Type-Other Patch-new
New issue 1888 by pkx1...@gmail.com: Introduce a maximum depth for markup
evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
http://codereview.appspot.com/5032041/
This will fix cases where a markup fu
