Re: [Lilypond-auto] Issue 3591 in lilypond: Making flat flags available

[lilypond]

Comment #17 on issue 3591 by address@hidden: Making flat flags available
http://code.google.com/p/lilypond/issues/detail?id=3591

This is all as expected.  _Including_ the changed commit id (a commit id  
references a given diff and all of the history, so a rebase will result in  
a different commit id).

It's my guess that baa9a1f25594917e9817aba61585a1a9caeeb217 was your  
personal repository's commit id before rebasing.

So you should always try posting the commit id/log entry right after  
pushing to staging.

Can you find the old id when doing git reflog in your personal repository?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings