Han-Wen Nienhuys <[email protected]> writes: > On Fri, Feb 7, 2020 at 6:54 PM David Kastrup <[email protected]> wrote: > >> I propose that I am going to pick up the pieces of >> not-actually-formally-reviewed patches making up the bulk of them and >> put them, Guilev2-guarded (so that they don't affect Guilev1 >> compilations) into staging->master without going through the formal >> processes. >> >> The reason to do that is that the current state already likely wasted >> considerable time of Han-Wen by finding solutions for problems that were >> already previously turned into non-showstoppers although not necessarily >> in the cleanest manner. But it would seem that even if part of them is >> likely to eventually be superseded, giving Han-Wen a better starting >> place would make him work and plan more effectively. >> > > Thanks, David! > > Can you mark the commits with some prefix ("GUILE2: blah") so they stand > out?
Sounds reasonable. Other comments? I'll try my best not to be disruptive in the process. It would likely have the effect of making Guile 2.21.0 a better starting place for experiments also for people not active in the loop. It's conceivable that part of the rationale for staying in a branch at that time was discouraging integrators from distributing sub-par versions of LilyPond compiled with Guile 2. If that was the motivation, it apparently has not helped since we got reports of such compilations... -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
