Re: aede-policy vs. new years

Are you updating every file from say
Copyright (C) 2010, foo inc
To
Copyright (C) 2013, foo inc

Or are you making the update the form as range ala
Copyright (C) 2010-2013, foo inc

There seems to be a lot of misinformation re copyright forms and meanings. What say your attorney ?

Sent from my iPhone

On Jan 3, 2013, at 3:45, "Aryeh Friedman" <[email protected]> wrote:

> Just passed that idea by our attorney and he said that we would loose
> any protection we had for code written in the new year unless *EVERY*
> file (regardless if it was modified or not in the new year) was
> updated with the new copyright year
>
> On Thu, Jan 3, 2013 at 2:51 AM, Walter Franzini
> <[email protected]> wrote:
>> On Tue, Jan 01 2013, Aryeh Friedman wrote:
>>
>>> Does anyone have a easy way of making sure that aede-policy does not
>>> complain in mass on copyright years right after new years (I do not
>>> want to do aefa foreign-copyright=true either... I prefer to actually
>>> have the right copyright notice)
>>
>> You can also use aca foreign-copyright=true, maybe it can fit better
>> with your workflow.
>>
>> ciao
>> --
>> walter franzini
> _______________________________________________
> Aegis-users mailing list
> [email protected]
> http://lists.auug.org.au/listinfo/aegis-users

This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your system.