Patch on countdown for May 28th
https://codereview.appspot.com/236450043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
Here is the current patch countdown list. The next countdown will be on
May 28th.
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
___
12:38:14 (UTC) Begin LilyPond compile, previous commit at
2df342bbb164aeb3de0ec17304de90d178f1fd52
12:38:18 test-master-lock and PID entry exist but previous Patchy
run (PID 10274) died, resetting test-master-lock anyway.
12:38:19 Merged staging, now at:2df342bbb164aeb3de0ec17304de90
Yes there is something that is breaking tyhe make process for patchy-staging
On 25/05/15 13:40, pat...@gnu.org wrote:
> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
> 2df342bbb164aeb3de0ec17304de90d178f1fd52
> 12:38:18 test-master-lock and PID entry exist but previous Patchy
> ru
On 2015/05/24 22:56:44, Keith wrote:
I think whiteout-stencil should simply call this function, with the
defaults
suggested, so that the existing
\set Xx.whiteout=##t and \markup\whiteout use this new method.
I’ve always been unhappy with the current method for whiteout (which I
have also bee
pat...@gnu.org writes:
> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
> 2df342bbb164aeb3de0ec17304de90d178f1fd52
> 12:38:18 test-master-lock and PID entry exist but previous Patchy
> run (PID 10274) died, resetting test-master-lock anyway.
> 12:38:19 Merged staging, now at:
On 25/05/15 14:18, David Kastrup wrote:
> pat...@gnu.org writes:
>
>> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
>> 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:38:18 test-master-lock and PID entry exist but previous Patchy
>> run (PID 10274) died, resetting test-master-lock a
Am 25. Mai 2015 15:18:46 MESZ, schrieb David Kastrup :
>pat...@gnu.org writes:
>
>> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
> 2df342bbb164aeb3de0ec17304de90d178f1fd52
>> 12:38:18 test-master-lock and PID entry exist but previous Patchy
>> run (PID 10274) died, resetting te
Look at page 22 of the most recent PDF of Learning, and you'll see that
whenever we use @notation{text}, then there is a paragraph break before
the "text". It took a while to figure out the guilty commit, but it is
9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from
upstream".
A
Phil Holmes writes:
> Look at page 22 of the most recent PDF of Learning, and you'll see that
> whenever we use @notation{text}, then there is a paragraph break before
> the "text". It took a while to figure out the guilty commit, but it is
> 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update t
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Monday, May 25, 2015 4:00 PM
Subject: Re: PDF is broken for @notation{} encoding
Phil Holmes writes:
> Look at page 22 of the most recent PDF of Learning, and you'll see that
> whenever we use @notation{text},
I've uploaded the patch
that can add Netpbm messages to verbose output.
http://code.google.com/p/lilypond/issues/detail?id=4420
https://codereview.appspot.com/240950043
Until now, the Netpbm message didn't appear in the verbose output.
Therefore, it was difficult to understand Netpbm error
like f
- Original Message -
From: "Phil Holmes"
To: "David Kastrup"
Cc:
Sent: Monday, May 25, 2015 4:08 PM
Subject: Re: PDF is broken for @notation{} encoding
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Monday, May 25, 2015 4:00 PM
Subject: Re: PDF is
[1][macupdate-logo.png]
top background
App Listing Updated
Hi lilypond.org, We have updated your application listing for LilyPond
2.19.21-1 on [2]MacUpdate.com. Please take a moment to review your
a
On 25/05/15 14:31, Urs Liska wrote:
>
>
> Am 25. Mai 2015 15:18:46 MESZ, schrieb David Kastrup :
>> pat...@gnu.org writes:
>>
>>> 12:38:14 (UTC) Begin LilyPond compile, previous commit at
>> 2df342bbb164aeb3de0ec17304de90d178f1fd52
>>> 12:38:18 test-master-lock and PID entry exist but previo
James Lowe writes:
> But it is a lot less than it ever was and apart from the odd
> fat-finger of pushing to master instead of staging (and Phil's recent
> GCC issue) we've not had any broken master builds.
>
> Hooray for HEAD:staging!
Well, one quasi regular source of broken builds in old times
On 2015/05/25 13:06:26, Valentin Villenave wrote:
So, ideally \whiteout should mimic this behavior rather than cover
stuff with a
layer of white paint. Not sure how to do that, though.
In my opinion, whiteout needs to create a layer of white paint. That's
what whiteout means. It's like us
I like what you've done.
I like Keith's suggestion for delayed stencil evaluation.
Thanks,
Carl
https://codereview.appspot.com/236480043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Apart from a really trivial nitpick, LGTM
(but I haven't checked if anything has been missed)
Trevor
https://codereview.appspot.com/239250043/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/239250043/diff/1/Document
There seems to be a way to do this as a simple expansion of
capabilities, so you do need to change existing input files. Have
\language"français" accept 'ré', and also 're' for backward
compatibility with the former use of Italian names.
https://codereview.appspot.com/239930043/diff/40001/Docum
On 2015/05/25 20:43:30, Carl wrote:
In my opinion, whiteout needs to create a layer of white paint.
That's what
whiteout means.
Well, "whiteout" is the name chosen by a couple modern Dutch
programmers, but we don't really want whiteout.
We want that thing that happens when you fill the neigh
The additional copies of the stencils do make the PDF files noticeably
larger. 8% larger when I used 16-copy whiteout around all dynamics and
text marks in a string quartet score.
The compilation time increased by 2%, desipte the repeated computations
of sines and cosines.
With \pointAndClickOn
Phil Holmes philholmes.net> writes:
> >> > whenever we use notation{text}, then there is a paragraph break
before
> >> > the "text". It took a while to figure out the guilty commit, but it is
> >> > 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex from
> >> > upstream".
> >> >
I
Phil Holmes philholmes.net> writes:
>
> I've managed to work out how to upgrade Ubuntu 10.04 to gcc 4.8.1
> with the help of StackOverflow, and can now compile again.
I'm still working on sorting out dependencies.
The troublesome macro asks is used in only three places, creating
in each place
Keith OHara writes:
> Phil Holmes philholmes.net> writes:
>
>>
>> I've managed to work out how to upgrade Ubuntu 10.04 to gcc 4.8.1
>> with the help of StackOverflow, and can now compile again.
>
> I'm still working on sorting out dependencies.
>
> The troublesome macro asks is used in only th
Keith OHara writes:
> Phil Holmes philholmes.net> writes:
>
>> >> > whenever we use notation{text}, then there is a paragraph break
> before
>> >> > the "text". It took a while to figure out the guilty commit, but it is
>> >> > 9f3c7711bb73baf3aea8502227fb5fd2d2851753: "update texinfo.tex fr
26 matches
Mail list logo
