Issue 4527: remove declarations of undefined callbacks (issue 251500043 by nine.fierce.ball...@gmail.com)

Reviewers: , Message: While working with David's script from this thread: http://lists.gnu.org/archive/html/lilypond-devel/2015-07/msg00096.html I noticed that a bunch of callbacks are declared but not defined. Description: remove declarations of undefined callbacks Please review this at https

Re: Add comment to font.scm and lilypond-fonts.conf.in (issue 257940043 by pkx1...@gmail.com)

On 2015/07/27 12:27:26, J_lowe wrote: On 2015/07/27 12:10:24, trueroad wrote: > https://codereview.appspot.com/257940043/diff/1/scm/font.scm > File scm/font.scm (right): > > https://codereview.appspot.com/257940043/diff/1/scm/font.scm#newcode254 > scm/font.scm:254: ; are aliases that are define

Re: Add comment to font.scm and lilypond-fonts.conf.in (issue 257940043 by pkx1...@gmail.com)

Reviewers: trueroad, Message: On 2015/07/27 12:10:24, trueroad wrote: https://codereview.appspot.com/257940043/diff/1/scm/font.scm File scm/font.scm (right): https://codereview.appspot.com/257940043/diff/1/scm/font.scm#newcode254 scm/font.scm:254: ; are aliases that are defined in mf/lilypo

Add comment to font.scm and lilypond-fonts.conf.in (issue 257940043 by pkx1...@gmail.com)

https://codereview.appspot.com/257940043/diff/1/scm/font.scm File scm/font.scm (right): https://codereview.appspot.com/257940043/diff/1/scm/font.scm#newcode254 scm/font.scm:254: ; are aliases that are defined in mf/lilypond-fonts.conf.in. `mf/lilypond-fonts.conf.in' is filename in the source fil

Re: can't use `git cl'

On 27/07/15 09:40, Werner LEMBERG wrote: >>> What's the status of `git cl upload'? It always fails with `incorrect >>> username or password'. I've eventually read the thread >>> >>> >>> http://lilypond.1069038.n5.nabble.com/git-cl-upload-has-stopped-working-td177113.html >>> >>> Is there any

Re: can't use `git cl'

Il giorno lun 27 lug 2015 alle 10:40, Werner LEMBERG ha scritto: It's not completely clear to me what you mean with `works again'. The old workflow of git-cl was adding a Rietveld issue and at the same time adding a Google Code entry for the lilypond project. Do I understand correctly that the

Re: can't use `git cl'

Werner LEMBERG writes: >>> What's the status of `git cl upload'? It always fails with `incorrect >>> username or password'. I've eventually read the thread >>> >>> >>> http://lilypond.1069038.n5.nabble.com/git-cl-upload-has-stopped-working-td177113.html >>> >>> Is there any outcome? Or do w

Re: can't use `git cl'

>> What's the status of `git cl upload'? It always fails with `incorrect >> username or password'. I've eventually read the thread >> >> >> http://lilypond.1069038.n5.nabble.com/git-cl-upload-has-stopped-working-td177113.html >> >> Is there any outcome? Or do we have to manually create Google

PATCHES: Countdown for July 30th 2015

Hello, Here is the current patch countdown list. The next countdown will be on July 30th. You can always view the most current countdown list here: http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch __

Re: can't use `git cl'

Hello, On 27/07/15 09:15, Werner LEMBERG wrote: > Folks, > > > What's the status of `git cl upload'? It always fails with `incorrect > username or password'. I've eventually read the thread > > > http://lilypond.1069038.n5.nabble.com/git-cl-upload-has-stopped-working-td177113.html > > Is ther

can't use `git cl'

Folks, What's the status of `git cl upload'? It always fails with `incorrect username or password'. I've eventually read the thread http://lilypond.1069038.n5.nabble.com/git-cl-upload-has-stopped-working-td177113.html Is there any outcome? Or do we have to manually create Google Code iss

Re: NR Changing Defaults: document \etc (issue 256990043 by d...@gnu.org)

https://codereview.appspot.com/256990043/diff/20001/Documentation/notation/changing-defaults.itely File Documentation/notation/changing-defaults.itely (right): https://codereview.appspot.com/256990043/diff/20001/Documentation/notation/changing-defaults.itely#newcode4769 Documentation/notation/ch