Hello,
Here is the current patch countdown list. The next countdown will be on
March 7th
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
***
Push:
5813 Remove unused .1 => .txt rule - Han-Wen Nienhuys
https:/
> The mentioned commit 7200d7365be was after stable/2.20 was branched
> and not backported AFAICS. This means both 2.19.84 and 2.20.0 use
> the "old" relocation algorithm that was not documented. So the
> files at lilypond.org are correct, even if that's maybe unfortunate
> in this case. This
Marnen Laibow-Koser writes:
> On Wed, Mar 4, 2020 at 3:50 PM David Kastrup wrote:
>
>> Marnen Laibow-Koser writes:
>>
>> > On Wed, Mar 4, 2020 at 3:14 PM David Kastrup wrote:
>> >
>
> [...]
>
>>
>> >> I think that it will cure itself once 2.21.0 is released. We had this
>> >> last time round
On Wed, Mar 4, 2020 at 4:42 PM David Kastrup wrote:
> Marnen Laibow-Koser writes:
>
[...]
>
> > OK, so the docs available on the website for the *current released
> > versions* are defective in the way Werner said and should be fixed. It
> > won’t do to just wait till 2.21 comes out.
>
> It wo
Am Mittwoch, den 04.03.2020, 21:14 +0100 schrieb David Kastrup:
> Werner LEMBERG <
> w...@gnu.org
> > writes:
>
> > > From: Marnen Laibow-Koser <
> > > mar...@marnen.org
> > > >
> > > Date: Wed, 4 Mar 2020 10:35:00 -0500
> > >
> > > > The search algorithm is actually documented in `usage.pdf`,
>
On Wed, Mar 4, 2020 at 3:50 PM David Kastrup wrote:
> Marnen Laibow-Koser writes:
>
> > On Wed, Mar 4, 2020 at 3:14 PM David Kastrup wrote:
> >
[...]
>
> >> I think that it will cure itself once 2.21.0 is released. We had this
> >> last time round I think.
> >>
> >> But the 2.20.0 version is
Marnen Laibow-Koser writes:
> On Wed, Mar 4, 2020 at 3:14 PM David Kastrup wrote:
>
>> Werner LEMBERG writes:
>>
>> >> From: Marnen Laibow-Koser
>> >> Date: Wed, 4 Mar 2020 10:35:00 -0500
>> >>
>> >>> The search algorithm is actually documented in `usage.pdf`,
>> >>
>> >> I’ve never seen that
On Wed, Mar 4, 2020 at 3:14 PM David Kastrup wrote:
> Werner LEMBERG writes:
>
> >> From: Marnen Laibow-Koser
> >> Date: Wed, 4 Mar 2020 10:35:00 -0500
> >>
> >>> The search algorithm is actually documented in `usage.pdf`,
> >>
> >> I’ve never seen that file. Where would I find it?
> >
> > Ouc
Werner LEMBERG writes:
>> From: Marnen Laibow-Koser
>> Date: Wed, 4 Mar 2020 10:35:00 -0500
>>
>>> The search algorithm is actually documented in `usage.pdf`,
>>
>> I’ve never seen that file. Where would I find it?
>
> Ouch. It should be at
>
> http://lilypond.org/doc/v2.19/Documentation/us
On Wed, Mar 4, 2020 at 1:15 PM Werner LEMBERG wrote:
> > From: Marnen Laibow-Koser
> > Date: Wed, 4 Mar 2020 10:35:00 -0500
> >
> >> The search algorithm is actually documented in `usage.pdf`,
> >
> > I’ve never seen that file. Where would I find it?
>
> Ouch. It should be at
>
>
> http://lily
On Wed, Mar 4, 2020 at 1:22 PM Werner LEMBERG wrote:
>
> >> OMG this is documented? I wish I’d known all this weeks ago when I
> >> was writing the Mac Makefile!
>
> FYI, here is the first part of the relocation documentation.
>
[snipped]
Thank you. This is really helpful and I'm going to revi
>> OMG this is documented? I wish I’d known all this weeks ago when I
>> was writing the Mac Makefile!
FYI, here is the first part of the relocation documentation.
There’s actually a second mechanism for run-time configuration:
LilyPond heavily relies on external programs and libraries, in
> From: Marnen Laibow-Koser
> Date: Wed, 4 Mar 2020 10:35:00 -0500
>
>> The search algorithm is actually documented in `usage.pdf`,
>
> I’ve never seen that file. Where would I find it?
Ouch. It should be at
http://lilypond.org/doc/v2.19/Documentation/usage-big-page.html#relocation
but it'
On Wed, Mar 4, 2020 at 10:05 AM Werner LEMBERG wrote:
>
> > From: Marnen Laibow-Koser
> >
> > I mean that it’s clearer who wrote what if you don’t delete the line
> > that says “Werner LEMBERG wrote:” :)
>
> Ah, my mailer doesn't generate that.
Maybe it’s worth seeing if you can set it to gen
> From: Marnen Laibow-Koser
>
> I mean that it’s clearer who wrote what if you don’t delete the line
> that says “Werner LEMBERG wrote:” :)
Ah, my mailer doesn't generate that.
>> IMHO, environment variables should be handled as being 'stronger'
>> than stuff in relocation files.
>
> I think I
On Tue, Mar 3, 2020 at 6:25 PM Werner LEMBERG wrote:
>
> > [A suggestion: you may want to keep attributions when trimming
> > quotes.]
>
> What exactly do you mean?
I mean that it’s clearer who wrote what if you don’t delete the line that
says “Werner LEMBERG wrote:” :)
>
> >> Let's assume t
I think I just finished fighting GUB to produce working binaries for
the next unstable LilyPond 2.21. Please review the PR and merge:
https://github.com/gperciva/gub/pull/71
I propose to ditch FreeBSD because the binaries are not working anyway
and darwin-ppc/linux-ppc which is 32 bit PPC and not r
Am Mittwoch, den 04.03.2020, 09:34 +0100 schrieb Han-Wen Nienhuys:
> On Sun, Mar 1, 2020 at 3:12 PM Jonas Hahnfeld <
> hah...@hahnjo.de
> > wrote:
> > For example, I'd very much like #5799 to be part of 2.21.0 to be able
> > to cross-compile to x86_64-w64-mingw32 and show-case a replacement for
> >
On Sun, Mar 1, 2020 at 3:12 PM Jonas Hahnfeld wrote:
> For example, I'd very much like #5799 to be part of 2.21.0 to be able
> to cross-compile to x86_64-w64-mingw32 and show-case a replacement for
> GUB. However I acknowledge that the changes have at least the potential
> to break the current pro
On 2020/03/04 07:54:46, hanwenn wrote:
> LGTM
Can you update the commit message though? I don't think there is a
security problem here.
Adding . in $PATH is a security problem on multi-user systems. In the
context of the build, you can regard this from two angles:
- you're executing in a known e
20 matches
Mail list logo
