On the other hand, we try to keep the advertised (c) on binaries up to date. 
About the only way to do that is to make updating the (c) date part of the build scripts, that's relatively easy on Windows as the resource file is text and gets compiled.

Which reminds me ... :{

Peter


-----owner-openssl-...@openssl.org wrote: -----
To: "openssl-dev@openssl.org" <openssl-dev@openssl.org>
From: "Salz, Rich"
Sent by: owner-openssl-...@openssl.org
Date: 06/17/2014 08:46AM
Subject: RE: [openssl.org #3373] [BUG] [WIN] DLL copyright message not synchronize for quite a while

For what it's worth, the policy at IBM (where I used to work, and where they know quite a few things about software intellectual property), is that you only update the copyright on an individual file *when you modify it.*

/r$

--  
Principal Security Engineer
Akamai Technologies, Cambridge, MA
IM: rs...@jabber.me; Twitter: RichSalz

:I"Ϯrm (Z+7zZ)1x hW^^%
&jם.+-1ځj:+vh
______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org

Reply via email to