>> We should run `make grand-replace` to update all copyright years.
>> Since this is a completely mechanical thing to do, I suggest to
>> submit the MR, wait until a build was successful, then immediately
>> merging and committing it, bypassing the normal reviewing cycle.
>> This should minimize
Am Donnerstag, dem 18.02.2021 um 17:41 +0100 schrieb Werner LEMBERG:
> > > We should run `make grand-replace` to update all copyright years.
> > > Since this is a completely mechanical thing to do, I suggest to
> > > submit the MR, wait until a build was successful, then
> > > immediately
> > > mer
> To be clear, I do *not* plan to run grand-replace.py on the stable
> branch. Instead I'll "just" update the few user-facing strings, in
> lily/main.cc:273 and scripts/*.
OK. I misunderstood.
Werner
Hello,
Here is the current patch countdown list. The next countdown will be on
February 20th.
A list of all merge requests can be found here:
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!653 Scoped lookup
