Hello,
Here is the current patch countdown list. The next countdown will be on
February 10th
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
Push:
5471 Improve relocation debug messages. - Werner LEMBERG
https://
> New: No new patches at this time.
Please put
https://sourceforge.net/p/testlilyissues/issues/5468/
into the loop – it contains a new, improved patch, and it seems that
I've reset the tags to wrong values so that it slipped your attention.
Werner
___
Folks,
while trying to find out why
https://sourceforge.net/p/testlilyissues/issues/5472/
doesn't work as expected, I stumbled across a problem that I'm not
able to locate since hours.
Consider this call (with the patch from issue #5472 applied), where
lilypond gets configured and compiled
Hi,
On 06.02.19 23:31, Knut Petersen wrote:
On 06.02.19 15:09, Werner LEMBERG wrote:
That leaves the two problems of
- LLVMgold.so in /usr/lib/bfd-plugins shadowing liblto_plugin.so
(I rm'ed LLVMgold.so there for the purpose of the above gub run.)
This is definitely *not* a gub issue. It'
On 2019/02/03 14:59:03, dan_faithful.be wrote:
While it is true that this algorithm yields chords that people call
inversions,
it does not yield every chord that might be so called.
Huh. Not having learned music theory in an English-speaking environment,
I must say I’m at a bit of a loss when
Hi Knut, hi folks,
On Mon 2019-01-28 13:53 +0100, Knut Petersen wrote:
> Please report success / fails with os / version / cpu info.
With this setup:
- PRs 53-60 (including update to PR 59 on January 27) applied to GUB,
- Ubuntu 14.05 LTS amd64, ran in a chroot from Fedora 29,
- an Intel Core 2 Du
On Feb 7, 2019, at 14:49, v.villen...@gmail.com wrote:
>
> That being said, no problem for adding index entries no matter what we
> end up choosing. Would anyone else have thoughts on the subject of
> \invertChords vs \rotateChords?
So that it’s clear: I have no firm objection to \invertChords.
On 2/6/19, 3:42 PM, "lilypond-devel on behalf of Knut Petersen"
wrote:
>> - the need to make sure that `python` calls a python2 interpreter.
> No idea how this could be solved elegantly. I guess it can't, so we
> have again something to document...
>
Use /usr/bin/env