Re: Issue 2024 in lilypond: Patch: Let #{ ... #} pass its $ handling to environment cloning

[lilypond]

Comment #22 on issue 2024 by address@hidden: Patch: Let #{ ... #} pass its $  
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024

Negative.  The commit changes the code behavior, adds convertrules, and  
executes them in order to keep regtests going.

Maybe you overlooked the code behavior change in the extensive Rietveld  
review, but the substructure of the commit (done as merge commit) makes the  
actual code change separate available as  
fecc5999e224304e9d54e48bc7a92cdbb123cd35

git log --graph displays this as

* commit cd229915fc873fdb6fd0125827452cb0ba0067a7
| Author: David Kastrup <address@hidden>
| Date:   Mon Nov 7 15:22:24 2011 +0100
|
|     Adapt docs to new $ and #{ ... #} behavior
|
*   commit 2a07e6101abd393b88f22309dcda0c7ed032d85c
|\  Merge: ccebc52 ccc4855
| | Author: David Kastrup <address@hidden>
| | Date:   Thu Nov 10 15:41:41 2011 +0100
| |
| |     Let #{ ... #} pass its $ handling to environment cloning and run  
convert
| |
| * commit ccc485525e63f68623bce1c3ca7a2d4fb6e94499
| | Author: David Kastrup <address@hidden>
| | Date:   Tue Nov 8 15:21:49 2011 +0100
| |
| |     Run update-with-convert-ly, and run convert-ly manually on scm/*.scm
| |
| * commit fecc5999e224304e9d54e48bc7a92cdbb123cd35
|/  Author: David Kastrup <address@hidden>
|   Date:   Sun Nov 6 19:15:27 2011 +0100
|
|       Let #{ ... #} pass its $ handling to environment cloning
|
|       Includes convertrules.py rules for dealing with #{ ... #} and for
|       removing uses of ly:export
|