Re: [Lilypond-auto] Issue 2558 in lilypond: Documentation suggestion: Including LilyPond files

[lilypond]

Comment #5 on issue 2558 by address@hidden: Documentation suggestion:  
Including LilyPond files
http://code.google.com/p/lilypond/issues/detail?id=2558

I am not overly keen on pulling changes of semantics into the 2.16 branch.   
If it is not much additional work over the already proposed changes,  
improving the documentation for 2.16 might make some sense.  As long as  
work on changing behavior on 2.17 has not yet started, one might as well  
commit it into master, and cherry-pick over to stable once it works out.