Hi,
first on a technical note: Many do not use the Nabble interface and they
can’t see to which old thread you are replying. It’s more helpful to
just open a new one.
On 08.02.2017 19:22, oldsap wrote:
I see this problem as well. The log message is:
warning: compressing over-full page by
Flaming Hakama by Elaine wrote Wednesday, February 08, 2017 9:12 PM
>I endeavored to start contributing to lilypond development.
Great!
> I've been following the steps in the contributor docs, and on the git-cl
> page instructs me:
>
> http://lilypond.org/doc/v2.19/Documentation/contributor/g
2017-02-08 14:37 GMT+01:00 David Nalesnik :
> I notice that the patch has gotten swept up into the review process.
> If you like, I will tell James to remove it, or maybe put it into
> waiting so I can figure out how to fix my machine? (It's already
> gotten a review!) I don't want to put you or
I endeavored to start contributing to lilypond development.
I've been following the steps in the contributor docs, and on the git-cl
page instructs me:
http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl
For the LilyPond issue tracker, please request a user account by sending an
em
I see this problem as well. The log message is:
warning: compressing over-full page by 31.9 staff-spaces
warning: page 5 has been compressed
This generates one system at the top of page 5 with signs of compression in
the lowest staff, then leaves a huge empty space, then a highly compressed
syst
Hi Harm,
On Tue, Feb 7, 2017 at 7:46 PM, Thomas Morley wrote:
> 2017-02-08 0:08 GMT+00:00 David Nalesnik :
>> Harm,
>>
>> On Tue, Feb 7, 2017 at 5:57 PM, Thomas Morley
>> wrote:
>>> 2017-02-08 0:26 GMT+01:00 David Nalesnik :
>>>
I don't want to put anyone to the trouble of shepherding
Hello,
Here is the current patch countdown list. The next countdown will be on
January 11th
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5046 Remove some dead code from issue 1504 - David Kastrup
https
