Re: grand copyright replacement

[David Kastrup]

Werner LEMBERG <address@hidden> writes:

>>> I'm going to run `scripts/build/grand-replace' to update all
>>> copyright years.  However, my test run shows that there are a bunch
>>> of files that aren't covered, for example
>>> `lily/part-combine-part-iterator.cc', which has the following
>>> copyright notice:
>>>
>>>   Copyright (C) 2015 Daniel Eble <address@hidden>
>>>
>>> Shall this be updated to
>>>
>>>   Copyright (C) 2015-2019 Daniel Eble <address@hidden>
>>>
>>> ?  Ditto for a bunch of other files...
>>
>> How come they aren't covered?
>
> `grand-replace.py' is very simplistic; it only updates last year's
> copyright year to the current one.
>
> So is it OK to simply update the missing cases?  Assuming we are
> running `grand-replace' next year again this would be (in almost all
> cases) a one-time job.

Generally I'm a bit skeptical regarding those updates where people might
have moved or even passed on, but that does not really hinge upon the
matched or non-matched pattern, so I'd say go ahead.

-- 
David Kastrup