Make \footnote a post-event

Make \footnote a post-event

Also run scripts/auxiliar/update-with-convert-ly.sh

The result should work, but for sanity's sake, this should be followed
by a manual conversion of all occurences of

<>\footnote ...
note-or-chord

into

note-or-chord\footnote ...

It would have been too error-prone to try detecting a suitable
note-or-chord sequence to move across automatically.

[Keith, 2012-05-10 06:53:33]

I like the way you showed the results of the convert-ly regexp on the docs. 

Step 1 looks good, and I hope you can find time to do the re-ordering by hand
for step 2.

http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-se...
File input/regression/collision-seconds.ly (right):

http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-se...
input/regression/collision-seconds.ly:1: \version "2.14.0"
convert-ly changed this because I mis-typed an older version number when
expanding this test.  I'll change it later to "2.15.34" unless you do it with
this commit.

[Graham Percival, 2012-05-10 13:16:10]

LGTM

[dak, 2012-05-14 14:57:29]

As you can see, this draft comment did not get out in time but was forgotten.

Looks like changing the version to 2.15.34 is now in your ballpark.

http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-se...
File input/regression/collision-seconds.ly (right):

http://codereview.appspot.com/6203044/diff/1018/input/regression/collision-se...
input/regression/collision-seconds.ly:1: \version "2.14.0"
On 2012/05/10 06:53:33, Keith wrote:
> convert-ly changed this because I mis-typed an older version number when
> expanding this test.  I'll change it later to "2.15.34" unless you do it with
> this commit.

Sounds rather like something you should directly push to staging.  I'll catch up
with it when rebasing.