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

[lilypond]

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

Regarding comment #14/#15
I've no idea what happened. Best guess might be a weird c/p error while  
posting comment #11

Btw,
to push I do:

git fetch
git rebase origin dev/<what-ever-branch>
git push origin HEAD:staging

as adviced here
http://lists.gnu.org/archive/html/lilypond-devel/2013-08/msg00423.html

When I now do
git log --oneline --decorate
I get an additional hint to the branch I used to develop the patch (opposed  
to other entries).
Example:
...
7975e96 (dev/flat-flags) Making flat flags available
b381556 Issue 3572: convert-ly should produce several backup files for each  
invokation
...

Is this expected behaviour?
Have I done it wrong?


--
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