Re: Two git-cl questions

- Original Message - From: "Simon Albrecht" To: "ly-devel" Sent: Monday, December 21, 2015 7:14 PM Subject: Two git-cl questions Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process:

Re: Two git-cl questions

2015-12-21 20:14 GMT+01:00 Simon Albrecht : > Hello, > > after a long time I’ve now tried and uploaded a patch again. Two questions > on the git cl process: > What exact value should I use for ‘Allura server’? I didn’t get that right. git config -e for me returns: ...

Re: Two git-cl questions

The editor that is opened depends on the EDITOR environment variable so you can use whatever you want. HTH Urs Am 21. Dezember 2015 20:14:57 MEZ, schrieb Simon Albrecht : >Hello, > >after a long time I’ve now tried and uploaded a patch again. Two >questions on the git

Re: Two git-cl questions

On 21.12.2015 22:09, Phil Holmes wrote: - Original Message - From: "Simon Albrecht" To: "ly-devel" Sent: Monday, December 21, 2015 7:14 PM Subject: Two git-cl questions Hello, after a long time I’ve now tried and uploaded a patch

Re: Two git-cl questions

On 21.12.2015 22:17, Thomas Morley wrote: 2015-12-21 20:14 GMT+01:00 Simon Albrecht : Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that right.

Re: Store accidental styles in an alist (issue 280510043 by simon.albre...@mail.de)

Sorry that this is such a large and convoluted patch. It had to be done this way. The actual functionality should be unchanged, only the structure is disentangled and made accessible for custom additions. In the course of action, I corrected one or two typos in comments – hope that’s OK. Should

Re: ly:moment<=? ??

On 21.12.2015 02:23, David Nalesnik wrote: On Sun, Dec 20, 2015 at 7:08 PM, Simon Albrecht > wrote: Hello, while getting to terms with the accidentalStyle code I found that it would be useful (currently only for

Two git-cl questions

Hello, after a long time I’ve now tried and uploaded a patch again. Two questions on the git cl process: What exact value should I use for ‘Allura server’? I didn’t get that right. And, please, is there a way to upload a patch and edit the message without vi? I have absolutely no experience

New Dutch PO file for 'lilypond' (version 2.19.26)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Dutch team of translators. The file is available at: http://translationproject.org/latest/lilypond/nl.po (We can arrange things so that

Where to edit "selected snippets"

Hi all, for a patch I'm currently finishing I have to update the documentation, concretely one of the "selected snippets". I'm not sure where I have to do that. Is that something I should do in Documentation/snippets or should that be done in the LSR? TIA Urs

Improve beam count handling with subdivided beams (issue 276560043 by g...@ursliska.de)

THe code looks good to me. Just some minor details to look at. https://codereview.appspot.com/276560043/diff/1/Documentation/snippets/new/subdividing-beams.ly File Documentation/snippets/new/subdividing-beams.ly (right):

Re: Where to edit "selected snippets"

Am 21.12.2015 um 22:19 schrieb Urs Liska: > Hi all, > > for a patch I'm currently finishing I have to update the documentation, > concretely one of the "selected snippets". > I'm not sure where I have to do that. Is that something I should do in > Documentation/snippets or should that be done in

git cl wording issue

Just used the current git-cl for the first time and noticed a *minor* glitch. This link in the console output: Ticket created at: https://sourceforge.net/rest/p/testlilyissues/issues/4704/ points to the raw (JSON?) data. In order to provide a useful clickable link the "rest/" should be

Re: Musicians prefer LilyPond scores, study finds

Le 17/12/2015 17:53, Francisco Vila a écrit : Hello, I just gained my PhD. My humble thesis tells the design and results of an experiment with a number of musicians, comparing lilypond scores with the originals which those scores were copied from. Congratulations! Now I will try to

Issue 2314 - workaround and patch

Hi everybody! Werner: You reported in 2012 that lilypond emits a space glyph referencing the century schoolbook font at the top of every page. David: At that time you were not sure if this is a bug. The problem is still present, and it definitely is a bug because that extra space glyph has a

lilypond-auto doesn't work correctly

Is it possible to resurrect correct functionality of the `lilypond-auto' list? Currently, no mails from allura are sent to it, which makes it sort of useless... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org