On Mon, May 30, 2016 at 9:53 PM, Dan Eble wrote:
> Here’s something else I could use help with. The person who wrote
> Midi_note decided that a negative (“unknown”?) Audio_dynamic should
> be treated as 90/127, whereas the person who wrote Midi_dynamic
> decided that a negative Audio_dynamic shoul
On Monday, 2016-05-30 at 21:53 -0400, Dan Eble wrote:
> Here’s something else I could use help with. The person who wrote
> Midi_note decided that a negative (“unknown”?) Audio_dynamic should
> be treated as 90/127, whereas the person who wrote Midi_dynamic
> decided that a negative Audio_dynamic
Thomas,
On Tue, May 31, 2016 at 2:09 PM, Thomas Morley-2 [via Lilypond] <
ml-node+s1069038n191273...@n5.nabble.com> wrote:
> I usually don't pay much attention to the log of simple `make`, but
> after our present doc-problems I took a closer look and noticed two
> instances of `Internal Error` he
I usually don't pay much attention to the log of simple `make`, but
after our present doc-problems I took a closer look and noticed two
instances of `Internal Error` here one of it:
Invoking "t1asm parmesan-noteheads20.pt1 parmesan-noteheads20.pfb"...
Invoking "/usr/bin/fontforge -script parmesa
On 2016/05/31 19:22:33, thomasmorley651 wrote:
I can't review your code (out of my depth), but while applying your
patch for
testing whether Ì can `make doc' again I noticed:
https://codereview.appspot.com/300820043/diff/20001/tex/texinfo.tex
File tex/texinfo.tex (right):
https://coderevi
I can't review your code (out of my depth), but while applying your
patch for testing whether Ì can `make doc' again I noticed:
https://codereview.appspot.com/300820043/diff/20001/tex/texinfo.tex
File tex/texinfo.tex (right):
https://codereview.appspot.com/300820043/diff/20001/tex/texinfo.tex#n
LGTM
https://codereview.appspot.com/299200043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
James writes:
> Although I hadn't noticed that I had the default values of j3 and it
> took nearly an hour to compile the doc
Luxury. https://www.youtube.com/watch?v=VKHFZBUTA4k>
> (no wonder people hate doing it, I had forgotten what it was like in
> the olden days when I used to do doc work
James writes:
> On 31/05/16 16:52, David Kastrup wrote:
>
>> That sounds like Lilydev and 32bit. I'd be interested to know whether
>> 64bit has improved.
>
> This was 64 bit.
Great.
> It is just that I still had default setting of the
> lilypond-patchy-config file is j3 from my restored build
On 31/05/16 16:52, David Kastrup wrote:
That sounds like Lilydev and 32bit. I'd be interested to know whether
64bit has improved.
This was 64 bit.
It is just that I still had default setting of the
lilypond-patchy-config file is j3 from my restored build environmenty
when we first had th
James writes:
> On 31/05/16 13:56, James wrote:
>>
>>
>> On 31/05/16 13:37, David Kastrup wrote:
>>> "Phil Holmes" writes:
>>>
Patchy-staging running now.
> https://codereview.appspot.com/297420043/
>>> Well, hooray! master has been pushed. Now let's see whether this helps
>>> James i
James writes:
> On 31/05/16 13:37, David Kastrup wrote:
>> "Phil Holmes" writes:
>>
>>> Patchy-staging running now.
https://codereview.appspot.com/297420043/
>> Well, hooray! master has been pushed. Now let's see whether this helps
>> James in any respect (if there is still a Ghostscript
hello
On 31/05/16 13:56, James wrote:
On 31/05/16 13:37, David Kastrup wrote:
"Phil Holmes" writes:
Patchy-staging running now.
https://codereview.appspot.com/297420043/
Well, hooray! master has been pushed. Now let's see whether this helps
James in any respect (if there is still a Gho
Il giorno mar 31 mag 2016 alle 9:35, Benkő Pál
ha scritto:
2016-05-31 8:15 GMT+02:00 Federico Bruni :
I could not push to a /dev/name/branch name. I had to use a short
name
without slashes:
git push origin translation:fedelibre-doc-it
while the following did not work:
git push origin t
14:30:36 (UTC) Begin LilyPond compile, previous commit at
905109ea0e90efa8d9c1ba02769e458a0707cc47
14:30:42 Merged staging, now at:905109ea0e90efa8d9c1ba02769e458a0707cc47
14:30:43Success:./autogen.sh --noconfigure
14:30:56Success:/tmp/
On 31/05/16 13:37, David Kastrup wrote:
"Phil Holmes" writes:
Patchy-staging running now.
https://codereview.appspot.com/297420043/
Well, hooray! master has been pushed. Now let's see whether this helps
James in any respect (if there is still a Ghostscript problem, it likely
won't, but o
"Phil Holmes" writes:
> Patchy-staging running now.
>>
>> https://codereview.appspot.com/297420043/
Well, hooray! master has been pushed. Now let's see whether this helps
James in any respect (if there is still a Ghostscript problem, it likely
won't, but otherwise it might).
And I need to sto
- Original Message -
From:
To: ;
Cc: ;
Sent: Tuesday, May 31, 2016 1:02 PM
Subject: Re: Delay import of `midi' module. (issue 297420043 by
lemzw...@googlemail.com)
Werner, do you think you can push a fixed version?
Done. For me, `make test` succeeded.
https://codereview.appspo
Patchy-staging running now.
--
Phil Holmes
- Original Message -
From:
To: ;
Cc: ;
Sent: Tuesday, May 31, 2016 1:02 PM
Subject: Re: Delay import of `midi' module. (issue 297420043 by
lemzw...@googlemail.com)
Werner, do you think you can push a fixed version?
Done. For me, `m
Werner, do you think you can push a fixed version?
Done. For me, `make test` succeeded.
https://codereview.appspot.com/297420043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
pat...@gnu.org writes:
> 10:35:41 (UTC) Begin LilyPond compile, previous commit at
> def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:55 Merged staging, now at: def633f7a88fe8950b685adee93165c42299bd5c
> 10:35:56 Success:./autogen.sh --noconfigure
> 10:36:13 Suc
"Phil Holmes" writes:
> - Original Message -
> From:
> To:
> Cc: ;
> Sent: Tuesday, May 31, 2016 11:37 AM
> Subject: Re: Delay import of `midi' module. (issue 297420043
> bylemzw...@googlemail.com)
>
>>> > Can you push this right to staging
>>
>>> Done.
>>
>> Aargh, I forgot to massag
OK, will fix that. Please remove the current patch from staging.
https://codereview.appspot.com/297420043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
- Original Message -
From:
To:
Cc: ;
Sent: Tuesday, May 31, 2016 11:37 AM
Subject: Re: Delay import of `midi' module. (issue 297420043
bylemzw...@googlemail.com)
> Can you push this right to staging
Done.
Aargh, I forgot to massage the commit message to mention the issue.
Sor
10:35:41 (UTC) Begin LilyPond compile, previous commit at
def633f7a88fe8950b685adee93165c42299bd5c
10:35:55 Merged staging, now at:def633f7a88fe8950b685adee93165c42299bd5c
10:35:56Success:./autogen.sh --noconfigure
10:36:13Success:/tmp/
Reviewers: ,
Description:
issue 4848: replace comma in URL with %2C entity
otherwise texinfo considers it as a comma delimiter of @uref
Please review this at https://codereview.appspot.com/294660043/
Affected files (+4, -4 lines):
M Documentation/es/web/community.itexi
M Documentation/fr/w
> Can you push this right to staging
Done.
Aargh, I forgot to massage the commit message to mention the issue.
Sorry for that.
https://codereview.appspot.com/297420043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/
Reviewers: dak,
Message:
Ok, running the script with just --version or --help does indeed not
need the midi module.
Yep.
This is ugly as whatever but likely will do the trick.
:-) Interestingly, I haven't find out yet how `midi.c' gets compiled
at all; I can't find any trace of it in the l
On 2016/05/31 07:13:04, dak wrote:
https://codereview.appspot.com/297420043/diff/1/scripts/midi2ly.py
File scripts/midi2ly.py (right):
https://codereview.appspot.com/297420043/diff/1/scripts/midi2ly.py#newcode925
scripts/midi2ly.py:925: import midi
Doesn't this merely work by chance?
If ru
10:02:01 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
10:02:05 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
10:02:06Success:./autogen.sh --noconfigure
10:02:25Success:/tmp/
09:52:20 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:52:24 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:52:25Success:./autogen.sh --noconfigure
09:52:39Success:/tmp/
09:47:21 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:47:25 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:47:26Success:./autogen.sh --noconfigure
09:47:40Success:/tmp/
09:34:56 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:35:10 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:35:11Success:./autogen.sh --noconfigure
09:35:11 *** FAILED BUILD ***
/tmp/li
09:38:31 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:38:35 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:38:36Success:./autogen.sh --noconfigure
09:38:54Success:/tmp/
09:33:49 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:33:54 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:33:54Success:./autogen.sh --noconfigure
09:33:55 *** FAILED BUILD ***
/tmp/li
pat...@gnu.org writes:
> 09:14:55 (UTC) Begin LilyPond compile, previous commit at
> dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
> 09:15:08 test-master-lock and PID entry exist but previous Patchy
> run (PID 17333) died, resetting test-master-lock anyway.
> 09:15:10 Merged staging, now at:
09:14:55 (UTC) Begin LilyPond compile, previous commit at
dbaf1e56e37be0e204231c5bf1adcb14bd8ac3b8
09:15:08 test-master-lock and PID entry exist but previous Patchy
run (PID 17333) died, resetting test-master-lock anyway.
09:15:10 Merged staging, now at:dbaf1e56e37be0e204231c5bf1adcb
James writes:
> Oh Well, Lilydev complains about the same make doc error when (I use
> -j5) - I am 99% sure, I haven't time now to look at the full output,
> but the messages generated on the console are so familiar that I am
> almost sure it is the same thing.
>
> I have to leave now for Home.
Federico Bruni writes:
> Hi all
>
> Last week I've worked on updating the italian translation.
> I always work on the translation branch and push to the translation
> branch. Sometimes I need to push my changes to a temporary branch on
> the server (because I want to make a backup before the week
2016-05-31 8:15 GMT+02:00 Federico Bruni :
> I could not push to a /dev/name/branch name. I had to use a short name
> without slashes:
>
> git push origin translation:fedelibre-doc-it
>
> while the following did not work:
>
> git push origin translation:/dev/fede/doc-it
>
> Not a big deal.. but I'd
https://codereview.appspot.com/297420043/diff/1/scripts/midi2ly.py
File scripts/midi2ly.py (right):
https://codereview.appspot.com/297420043/diff/1/scripts/midi2ly.py#newcode925
scripts/midi2ly.py:925: import midi
Doesn't this merely work by chance?
If running the script depends on the midi mod
41 matches
Mail list logo
