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
[email protected] wrote: -----
To: "[email protected]" <[email protected]>
From: "Salz, Rich"
Sent by: [email protected]
Date: 06/17/2014 08:46AM
Subject: RE: [openssl.org #3373] [BUG] [WIN] DLL copyright message not synchronize for quite a while
From: "Salz, Rich"
Sent by: [email protected]
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: [email protected]; Twitter: RichSalz
:I"Ϯrm (Z+7zZ)1x hW^^%
&jם.+-1ځj:+vh
/r$
--
Principal Security Engineer
Akamai Technologies, Cambridge, MA
IM: [email protected]; Twitter: RichSalz
:I"Ϯrm (Z+7zZ)1x hW^^%
&jם.+-1ځj:+vh
