PATCHES - Countdown to October 10

Here is the current countdown report. The next countdown, for which we Canadians will be truly thankful, will begin on October 10th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1656 Fix \alterBroken

Re: Administration of mailing lists

David Kastrup writes: > Jean Abou Samra writes: > >> Thus I wrote to the general GNU list server admins and proposed >> to step up for being an admin on these lists, just like I am >> already an admin on lilypond-user-fr (the French-speaking equivalent >> of lilypond-user, in case you didn't

Re: Administration of mailing lists

> On Oct 7, 2022, at 4:47 PM, Dan Eble wrote: > > On Oct 7, 2022, at 16:45, Jean Abou Samra wrote: > >> Thus I wrote to the general GNU list server admins and proposed >> to step up for being an admin on these lists, just like I am >> already an admin on lilypond-user-fr (the

Re: Administration of mailing lists

Jean Abou Samra writes: > Thus I wrote to the general GNU list server admins and proposed > to step up for being an admin on these lists, just like I am > already an admin on lilypond-user-fr (the French-speaking equivalent > of lilypond-user, in case you didn't know). > > Is that OK with

Re: Administration of mailing lists,Administration of mailing lists

> Is that OK with everyone? +1 Werner

Re: To branch or not to branch

On Oct 7, 2022, at 13:51, Jonas Hahnfeld via Discussions on LilyPond development wrote: > > On Thu, 2022-10-06 at 08:39 +0200, Jean Abou Samra wrote: >> A factor that I was starting to forget in my enthusiasm for branching is >> !1510 (source locations). Here I am guilty of taking forever to

Re: Administration of mailing lists

On Oct 7, 2022, at 16:45, Jean Abou Samra wrote: > Thus I wrote to the general GNU list server admins and proposed > to step up for being an admin on these lists, just like I am > already an admin on lilypond-user-fr (the French-speaking equivalent > of lilypond-user, in case you didn't know). >

Re: Tablature full notation rests and aethstetics

> I'm only familiar with a subset of C++ up to C++03. Would my lack of > knowledge of modern C++ exclude me from being a contributor? No. Others will review your code and suggest using new features where it is appropriate. > I'm also not an expert on UB in C++, although I very much want to

Administration of mailing lists

Hi, This email is cross-posted to lilypond-user, lilypond-devel and bug-lilypond. The admin for these three lists (d...@gnu.org, apparently David R. Linn) has not been active in the project for a long time, and I have not been able to reach him by email. This is problematic because you need an

Re: To branch or not to branch

On Thu, 2022-10-06 at 08:39 +0200, Jean Abou Samra wrote: > A factor that I was starting to forget in my enthusiasm for branching is > !1510 (source locations). Here I am guilty of taking forever to prepare > the latest version of that patch. I am open to opinions on whether it > should be

Re: Tablature full notation rests and tablature aethstetic improvements

> In scores I've seen with circled tablature numbers, collisions between > numbers and circles are avoided by shifting numbers out of a straight > vertical column, which I suspect is quite different than how tablature is > currently handled internally and might require significant effort to >

Re: Tablature full notation rests and tablature aethstetic improvements

Hi, Am Fr., 7. Okt. 2022 um 07:44 Uhr schrieb tk5wbps2--- via Discussions on LilyPond development : > > I'm considering contributing to lilypond. > welcome to the pond > > The two features I propose are as follows. > > 1) An option to include rests in tablature (with \tabFullNotation). > Afaict,