Re: [PATCH] maint: fix copyright dates that were munged by a maintenance script

[Eric Blake]

On 11/08/2010 09:48 AM, Jim Meyering wrote:
> Also relevant, here are some relatively new
> guidelines from maintain.texi:
> 
>     ...
>     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.
> 
>     ...
>     You can use a range (@samp{2008-2010}) instead of listing individual
>     years (@samp{2008, 2009, 2010}) if and only if: 1)@tie{}every year in
>     the range, inclusive, really is a ``copyrightable'' year that would be
>     listed individually; @emph{and} 2)@tie{}you make an explicit statement
>     in a @file{README} file about this usage.

And piecing these two sentences together - the convention has been that
if your VCS is publicly visible, then the global copyright change at the
beginning of the year can be treated as a copyrightable changes, since
you have immediately published the change via the public access to the
VCS, even if you don't have a formal release of the package during that
year, and even if that particular file is untouched for the remainder of
the year.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature