On Mon, 3 Jan 2011, Joel E. Denny wrote: > On Sun, 2 Jan 2011, Joel E. Denny wrote: > > > From: Joel E. Denny <[email protected]> > > Date: Sun, 2 Jan 2011 08:17:44 -0500 > > Subject: [PATCH 2/3] 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
Actually, it's the maintainers document not the coding standards. I fixed that by pushing the following to master and branch-2.5. >From 15fe6bb421f00932e92a1d5bacaf1d4cefa0522d Mon Sep 17 00:00:00 2001 From: Joel E. Denny <[email protected]> Date: Mon, 3 Jan 2011 18:37:56 -0500 Subject: [PATCH] * ChangeLog (2011-01-02): improve description. --- ChangeLog | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 72605b2..6d83321 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2011-01-03 Joel E. Denny <[email protected]> + * ChangeLog (2011-01-02): improve description. + +2011-01-03 Joel E. Denny <[email protected]> + maint: don't update copyright years in bootstrap. * .x-update-copyright: Add entry for bootstrap. * bootstrap: Remove 2011 from copyright years. The bootstrap @@ -14,10 +18,11 @@ 2011-01-02 Joel E. Denny <[email protected]> - maint: prepare to use date ranges in copyright notices. + maint: prepare to use year 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. + notation. The GNU maintainers document requires this explanation: + <http://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices>. + I copied our explanation 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. -- 1.7.0.4
