copyright years

[David Glasser <gl...@mit.edu>]

Bumping copyright years when we edit a file is a pain, and I don't see
instructions to do so in HACKING.  Should we just update them en masse
yearly?

--dave

-- 
David Glasser | glasser@mit.edu | http://www.davidglasser.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: copyright years

[Peter Lundblad <pl...@google.com>]

David Glasser writes:
> Bumping copyright years when we edit a file is a pain, and I don't see
> instructions to do so in HACKING.  Should we just update them en masse
> yearly?
> 

This came up almost a year ago, so there should be a thread about it
in the archives. The end result was that no one did a sweep update
(because for the information to be accurate, you have to analyze the
logs to see if a file was actually changed(. Some of us, started using
the automatic copyright feature of our editor (emacs), which was quite
unpainful IMO.

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: copyright years

[Malcolm Rowe <ma...@farside.org.uk>]

On Thu, Nov 23, 2006 at 10:03:35AM -0500, David Glasser wrote:
> Bumping copyright years when we edit a file is a pain, and I don't see
> instructions to do so in HACKING.  Should we just update them en masse
> yearly?
> 

No.  Although we have done this before (2003? 2004?), doing so is a lie
if the file hasn't been changed in that year.  It's better to forget to
update the year, since that doesn't really have any downsides (assuming
we eventually correct it).

I use Julian Foad's check-copyright script in my pre-commit process.

Regards,
Malcolm