[libvirt] [TCK PATCH] maint: use correct Red Hat copyright

[Jim Meyering]

Daniel P. Berrange wrote:
> On Tue, Mar 30, 2010 at 02:35:46PM -0600, Eric Blake wrote:
>> * scripts/domain/050-transient-lifecycle.t: Correct the copyright
>> line.
>> * scripts/domain/051-transient-autostart.t: Likewise.
>> * scripts/domain/060-persistent-lifecycle.t: Likewise.
>> * scripts/domain/061-persistent-autostart.t: Likewise.
>> * scripts/domain/065-persistent-redefine.t: Likewise.
>> * scripts/domain/070-transient-to-persistent.t: Likewise.
>> * scripts/domain/080-unique-id-define.t: Likewise.
>> * scripts/domain/081-unique-id-create.t: Likewise.
>> * scripts/domain/090-invalid-ops-when-inactive.t: Likewise.
>> * scripts/domain/100-transient-save-restore.t: Likewise.
>> * scripts/domain/101-persistent-save-restore.t: Likewise.
>> * scripts/domain/102-broken-save-restore.t: Likewise.
>> * scripts/domain/120-disks-stats.t: Likewise.
>> * scripts/domain/200-disk-hotplug.t: Likewise.
>> * scripts/domain/205-disk-hotplug-ordering.t: Likewise.
>> * scripts/domain/210-nic-hotplug.t: Likewise.
>> * scripts/domain/215-nic-hotplug-many.t: Likewise.
>> * scripts/domain/240-usb-host-hotplug.t: Likewise.
>> * scripts/domain/250-pci-host-hotplug.t: Likewise.
>> * scripts/qemu/100-disk-encryption.t: Likewise.
>> * scripts/storage/100-create-vol-dir.t: Likewise.
>> * scripts/storage/200-clone-vol-dir.t: Likewise.
>>
>> Signed-off-by: Eric Blake <eblake at redhat.com>
>> ---
>>
>> This probably counts as trivial, but since this is my first
>> libvirt-tck patch, I thought I'd ask first.
>
> The intent is fine, but most of these scripts have not been
> touched in 2010, so shouldn't have their copyright date extended

That policy has been changed.
Now, it's recommended to update all files once per year,
regardless of whether they've been changed in that particular year.

http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices

    To update the list of year numbers, add each year in which you have made
    nontrivial changes to the package. (Here we assume you're using a
    publicly accessible revision control server, so that every revision
    installed is also immediately and automatically published.) When you add
    the new year, it is not required to keep track of which files have seen
    significant changes in the new year and which have not. It is
    recommended and simpler to add the new year to all files in the package,
    and be done with it for the rest of the year.