> 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 success
>> 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 reviewi
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
>
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 committin
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
Hello,
I noticed this command
http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies
:)
So I tried it...
Gosh... that command touches 'one or two' files doesn't it!
chuckle
Umm.. I guess this is something that a 'senior' dev probably should do
as it also touches all the
On Sun, Jan 08, 2012 at 09:53:16PM +, James wrote:
http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies
thanks, run.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
