Re: Issue 2346 in lilypond: Use convert-ly from latest development release for LSR updates

[lilypond]

Updates:
        Labels: -Fixed_2_15_31 Fixed_2_15_32

Comment #10 on issue 2346 by address@hidden: Use convert-ly from latest  
development release for LSR updates
http://code.google.com/p/lilypond/issues/detail?id=2346

git log origin --decorate --graph shows the following:
* commit 55d9ad39acee4288ee0d36230f70110b02546ab3
| Author: Graham Percival <address@hidden>
| Date:   Wed Feb 29 15:59:44 2012 +0000
|
|     Release: bump version.
|
*   commit 4493eb4584f92123ebacf51541ace8c0e20f5e5a
|\  Merge: 2411d0e ea270d9
| | Author: Graham Percival <address@hidden>
| | Date:   Wed Feb 29 15:59:33 2012 +0000
| |
| |     Merge branch 'release/unstable' into HEAD
| |
| * commit ea270d91e363a855827930c7b5b71a105aed922a (tag:  
release/2.15.31-1, ori
| | Author: Graham Percival <address@hidden>
| | Date:   Wed Feb 29 12:09:32 2012 +0000
| |
| |     Release: update news.
| |
* | commit 2411d0e11c5ca03997122c905bc2e58ea6a8682e
|/  Author: Janek Warchoł <address@hidden>
|   Date:   Sat Feb 25 08:11:10 2012 +0100
|
|       CG: Use latest convert-ly for LSR updates (fix 2346)
|
|       Suggested by Thomas Morley:
|       Use convert-ly from latest development release for LSR updates
|
* commit c8be1e28e0dab3c7707242336d76350c2f2f19eb (test-staging, ledger)

So this fix missed the release branch and has not made it into 2.15.31 even  
though it is in current master.  This small time window is the rare  
exception where
git show 2411d0e11c5ca03997122c905bc2e58ea6a8682e:VERSION
displays an inaccurate result: it is after the branch of the release, but  
before the bump in VERSION happened.