On Fri, Mar 13, 2020 at 2:02 AM Jonas Hahnfeld wrote:
> I'm still not convinced that we need compatibility code, but I'm happy
> with anything that gets us to a release and is not technically wrong.
By the way, from a Debian package maintainer point of view, breaking
backward compatibility is OK
On Sun, Mar 8, 2020 at 8:08 AM David Kastrup wrote:
>
> Anthony Fok writes:
>
> > Dear all,
> >
> > Thank you all for your kind considerations to system integrators like me.
> > :-D
> >
> > I recently submitted a patch to Denemo to get its configure.ca to
> > check for (hence support)
Dan Eble writes:
> On Mar 13, 2020, at 09:03, pkx1...@posteo.net wrote:
>>
>> 5703 Run scripts/auxiliar/fixcc.py - David Kastrup
>> https://sourceforge.net/p/testlilyissues/issues/5703
>> http://codereview.appspot.com/549480043
>
> What is the plan for this?
It's applied in 2.20. I probably
On Mar 13, 2020, at 09:03, pkx1...@posteo.net wrote:
>
> 5703 Run scripts/auxiliar/fixcc.py - David Kastrup
> https://sourceforge.net/p/testlilyissues/issues/5703
> http://codereview.appspot.com/549480043
What is the plan for this?
—
Dan
On Mar 13, 2020, at 04:43, Kevin Barry wrote:
>
> The direction of this statement is correct, but the magnitude is not. The
> kernel is still provided by the host. Getting a crash report can be
> frustrating when the guest's behavior hinges on /proc features that the host
> OS has
Hello Harm,
thanks for the answers.
>> (2) Will the LSR be re-imported into the LilyPond git repository
>> before the 2.21 release?
>
> Someone has to do it, if this is wished.
I think this would be beneficial. David?
>> (3) When will the LSR be updated to use LilyPond 2.20?
>
>
On 2020/03/13 13:33:29, hanwenn wrote:
> LGTM
>
> typo in the commit message
Done.
https://codereview.appspot.com/553690043/
Am Fr., 13. März 2020 um 14:54 Uhr schrieb Werner LEMBERG :
>
>
> Folks,
>
>
> three questions regarding the LSR.
>
> (1) Will the PNG images shown in the LSR automatically be regenerated
> if a snippet gets updated? Or do I have to do something?
Will happen automatically.
Sometimes with
Am Freitag, den 13.03.2020, 19:50 +0100 schrieb Francisco Vila:
> El 8/3/20 a las 18:33, Jonas Hahnfeld escribió:
> > Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles
> > Malahieude:
> > > Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit :
> > > > Am Samstag, den 07.03.2020, 11:27 +0100
El 8/3/20 a las 18:33, Jonas Hahnfeld escribió:
Am Sonntag, den 08.03.2020, 18:29 +0100 schrieb Jean-Charles
Malahieude:
Le 08/03/2020 à 18:16, Jonas Hahnfeld a écrit :
Am Samstag, den 07.03.2020, 11:27 +0100 schrieb Jean-Charles
Malahieude:
Hi all,
As I'm done with the French translations
On 3/13/2020 12:37 AM, Owen Lamb wrote:
I'm interested in applying for a GSoC project.
Any suggestions on where to start / who to talk to?
Thanks for your interest! Urs Liska leads most of the GSOC efforts. He
follows this list, so you've already found the best place to begin.
--
Karlin
Hi all,
I'm new here--been using LilyPond and Frescobaldi for a month or so, and
I'm loving it. Being an undergrad music composition major and a coding
hobbyist (experience with Java & JS and a smattering of Python, C#, C++,
Haskell, and LilyPond's Scheme), I'm interested in applying for a GSoC
Werner LEMBERG writes:
> Folks,
>
>
> three questions regarding the LSR.
>
> (1) Will the PNG images shown in the LSR automatically be regenerated
> if a snippet gets updated? Or do I have to do something?
>
> (2) Will the LSR be re-imported into the LilyPond git repository
> before the
Han-Wen Nienhuys writes:
> On Wed, Mar 11, 2020 at 11:56 PM David Kastrup wrote:
>>
>>
>> I am not particularly surprised, to be honest: it did seem like the
>> website would employ something other than the online-root/offline-root
>> targets in the normal Stepmake build procedure.
>>
>> The
The website uses scripts that aren't directly checked out from
savannah, so you can't directly compromise the webserver through code
commits.
I can update the scripts.
On Wed, Mar 11, 2020 at 11:56 PM David Kastrup wrote:
>
>
> I am not particularly surprised, to be honest: it did seem like the
Folks,
three questions regarding the LSR.
(1) Will the PNG images shown in the LSR automatically be regenerated
if a snippet gets updated? Or do I have to do something?
(2) Will the LSR be re-imported into the LilyPond git repository
before the 2.21 release?
(3) When will the LSR
https://codereview.appspot.com/565750043/diff/557620047/scm/define-music-types.scm
File scm/define-music-types.scm (right):
https://codereview.appspot.com/565750043/diff/557620047/scm/define-music-types.scm#newcode685
scm/define-music-types.scm:685: . ((description . "A transition between
lyric
LGTM
typo in the commit message
https://codereview.appspot.com/553690043/
Il giorno ven 13 mar 2020 alle 14:08, Jonas Hahnfeld
ha scritto:
Am Freitag, den 13.03.2020, 13:59 +0100 schrieb Federico Bruni:
Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld <
hah...@hahnjo.de
>
ha scritto:
> The usage of plain archives has the advantage that the user can
>
Hello,
Here is the current patch countdown list. The next countdown will be on
March 15th.
A quick synopsis of all patches currently in the review process can be
found here:
http://philholmes.net/lilypond/allura/
***
Push:
5837 Web: update and document documentation symlinks -
Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld
ha scritto:
The usage of plain archives has the advantage that the user can
install
and move the files anywhere, without invoking any installer. That is
by
design, but maybe there's a valid use case for installers that I'm
missing?
Am Freitag, den 13.03.2020, 13:59 +0100 schrieb Federico Bruni:
> Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld <
> hah...@hahnjo.de
> >
> ha scritto:
> > The usage of plain archives has the advantage that the user can
> > install
> > and move the files anywhere, without invoking any
Il giorno gio 12 mar 2020 alle 14:39, Jonas Hahnfeld
ha scritto:
I think this one actually has the same root case as
Karlin reported: I traced this back to the garbage collector freeing
objects prematurely. Apparently it's not really happy that I made it
unaware of threading...
I've just
Kevin Barry writes:
>>
>>
>> The direction of this statement is correct, but the magnitude is not. The
>> kernel is still provided by the host. Getting a crash report can be
>> frustrating when the guest's behavior hinges on /proc features that the
>> host OS has configured appropriately for
On Thu, Mar 12, 2020 at 6:17 PM David Kastrup wrote:
>
> Kevin Barry writes:
>
> >>
> >>
> >> Frankly, I am more sympathetic to "worksforme" discussions among
> >> developers than telling users "worksforme". Where is the point in being
> >> able to tell users that no developer will reproduce
>
>
> The direction of this statement is correct, but the magnitude is not. The
> kernel is still provided by the host. Getting a crash report can be
> frustrating when the guest's behavior hinges on /proc features that the
> host OS has configured appropriately for the host, not the guest.
>
Am Sonntag, den 08.03.2020, 16:40 +0100 schrieb Jonas Hahnfeld:
> Am Sonntag, den 08.03.2020, 16:28 +0100 schrieb David Kastrup:
> > So I am reasonably confident that with some reasonably designed chunks
> > of code, we'd end up with comparatively small headaches in upkeep. My
> > own gut feeling
27 matches
Mail list logo
