* README (Copyright statements): New section explaining the range
notation. The GNU coding standards require this explanation. I
copied ours from coreutils.
* build-aux/update-b4-copyright: Revert 2010-06-17 changes that
disabled Bison's automated use of ranges.
* cfg.mk (update-copyright-env): Likewise.
(cherry picked from commit
cb3f7f335aa69ba3e6478fea8d4591f4f6d43bc5)
+2011-01-02 Joel E. Denny <joeldenny@joeldenny.org>
+
+ maint: prepare to use date ranges in copyright notices.
+ * README (Copyright statements): New section explaining the range
+ notation. The GNU coding standards require this explanation. I
+ copied ours from coreutils.
+ * build-aux/update-b4-copyright: Revert 2010-06-17 changes that
+ disabled Bison's automated use of ranges.
+ * cfg.mk (update-copyright-env): Likewise.
+
2011-01-02 Joel E. Denny <joeldenny@joeldenny.org>
Correct my email address.
version number from `bison --version', and a complete, self-contained
test case in each bug report.
+* Copyright statements
+For any copyright year range specified as YYYY-ZZZZ in this package,
+note that the range specifies every single year in that closed interval.
+
Local Variables:
mode: outline
# Put spaces after commas.
$year_lines =~ s/, ?/, /g;
- # Do not compress to intervals; for example, do not replace
- # "2008, 2009, 2010" with "2008-2010". See the Copyright
- # Notices section in Information for Maintainers of GNU Software, at:
- # http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices
+ # Compress to intervals.
+ $year_lines =~
+ s/
+ (\d{4})
+ (?:
+ (,\ |-)
+ ((??{
+ if ($2 eq '-') { '\d{4}'; }
+ elsif (!$3) { $1 + 1; }
+ else { $3 + 1; }
+ }))
+ )+
+ /$1-$3/gx;
# Format within margin.
my $year_lines_new;
update-copyright: update-b4-copyright update-package-copyright-year
update-copyright-env = \
- UPDATE_COPYRIGHT_FORCE=1
+ UPDATE_COPYRIGHT_FORCE=1 UPDATE_COPYRIGHT_USE_INTERVALS=1