Janneke Nieuwenhuizen writes: Hello,
> We accidentally pushed a problematic set of commits to GNU Mes > branch. Staging has the last working commit > > d997c1df6590c62364232ae4d97807cc0847ba22 > build: Post-release update. > > We have a strict every-commit passes-the-regression-test policy, which > was broken by this push. > > Could you either enable non-fast-forwarding commits on dezyne master, or > reset master to current staging? This should have read, of course: Could you either enable non-fast-forwarding commits on MES master, or reset master to current staging? Greetings, Janneke -- Janneke Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond https://LilyPond.org Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
