> 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
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
>> 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 Mittwoch, dem 17.02.2021 um 08:25 +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 merging
> and committing it
Am 17.02.2021 um 14:11 schrieb Dan Eble:
On Feb 17, 2021, at 02:25, Werner LEMBERG wrote:
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
On Feb 17, 2021, at 02:25, Werner LEMBERG wrote:
>
> 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
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 the hassles w
