Re: running `make grand-replace`
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, bypassing the normal reviewing cycle. This should > minimize the hassles with additional rebasing of future MRs. > > Objections? Sounds good. On a related note, I think I'll also bump the years of user-visible messages in stable/2.22 to say 2021 instead of 2020. I forgot this for 2.22.0, but we can have it for a potential bugfix release. Does this make sense? Jonas signature.asc Description: This is a digitally signed message part
Re: running `make grand-replace`
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 and committing it, bypassing the normal reviewing cycle. This should minimize the hassles with additional rebasing of future MRs. Objections? no objection +1 — Dan
Re: running `make grand-replace`
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 normal reviewing cycle. This should > minimize the hassles with additional rebasing of future MRs. > > Objections? no objection — Dan
