To: nore...@sourceforge.net
Sent: 14/07/2019 20:23:46
Subject: [testlilyissues:issues] Moderation action required
The following submission requires approval at
https://sourceforge.net/p/testlilyissues/issues/_discuss/moderate before it can
be approved for posting:'t
Also reported on Mac OS (at least 10.1
Hello
On Sat, 12 May 2018 09:24:17 +0200, David Kastrup wrote:
> "James Lowe" writes:
>
> > Dev team,
> >
> > Don tacked a patch on the end of an already-fixed issue.
> >
> > https://sourceforge.net/p/testlilyissues/issues/5243
> >
> > I assume this needs a new issue?
>
> Basically yes, and
I don't think we should update a release last issued 5 years ago - so no 2.18.3.
It also seems that a security problem with no reported problems actually
happening in 5 years can be so serious to warrant rushing out a new release?
The problem is known, it is published how to exploit the
urday, May 12, 2018 11:27 AM
Subject: Re: [testlilyissues:issues] Moderation action required
Knut Petersen <knut_peter...@t-online.de> writes:
Am 12.05.2018 um 09:16 schrieb James Lowe:
Dev team,
Don tacked a patch on the end of an already-fixed issue.
James, they try to fix lilypond 2.18, n
David Kastrup wrote 12/05/2018 11:27:40
James, they try to fix lilypond 2.18, not 2.20 or master.
2.18 is still insecure.
At this point of time we probably really need to decide to release
2.20,
come hell and high water, including its current faults.
Or pitch out 2.18.3. At the very
Knut Petersen writes:
> Am 12.05.2018 um 09:16 schrieb James Lowe:
>> Dev team,
>>
>> Don tacked a patch on the end of an already-fixed issue.
>
> James, they try to fix lilypond 2.18, not 2.20 or master.
>
> 2.18 is still insecure.
At this point of time we probably
Am 12.05.2018 um 09:16 schrieb James Lowe:
Dev team,
Don tacked a patch on the end of an already-fixed issue.
James, they try to fix lilypond 2.18, not 2.20 or master.
2.18 is still insecure.
Knut
___
lilypond-devel mailing list
Don,
On Sat, 12 May 2018 09:24:17 +0200, David Kastrup wrote:
> "James Lowe" writes:
>
> > Dev team,
> >
> > Don tacked a patch on the end of an already-fixed issue.
> >
> > https://sourceforge.net/p/testlilyissues/issues/5243
> >
> > I assume this needs a
"James Lowe" writes:
> Dev team,
>
> Don tacked a patch on the end of an already-fixed issue.
>
> https://sourceforge.net/p/testlilyissues/issues/5243
>
> I assume this needs a new issue?
Basically yes, and definitely with an explanation of why the committed
fix is not
Dev team,
Don tacked a patch on the end of an already-fixed issue.
https://sourceforge.net/p/testlilyissues/issues/5243
I assume this needs a new issue?
Let me know.
James
On Fri, 11 May 2018 16:52:11 -, "Don Armstrong"
wrote:
> The following
10 matches
Mail list logo