Updating year of Copyright disclaimer from 2013 to 2014. #3944

Minor change, just updating copyright disclaimer from 2013 to 2014.

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/17a326b88cb2d117fbc82c2aa107b328119a59a2 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.

The copyright headers have already been updated for 2014 in #3646. The files your proposing changes to are files that haven't been modified this year, an thus don't need the copyright header changed.

Indeed. Only update copyright headers when something in the code changed in that year.

Note that the copyright headers in src/test and qa/ were added recently, so the adding of those headers doesn't count towards the year either.

Thank you for the explanation, I'm sorry for the mistake.

It's also unnessesary to write "Copyright (c)" since the (c) is supposed to replace the word copyright. But that seems to be our practice now.

I vaguely remember that historically the reason that Copyright (C) is used in software is that (C) in itself is not the real copyright symbol and thus may not be valid in court. (There is ©, but using non-ASCII characters in C/C++ source is still non-portable)

But even if not strictly necessary anymore, please don't do an all-over-the-place update for this.

(Note you no longer have to make any copyright notice, at all, to have a valid copyright)

@laanwj I realise we're getting off topic, but if "(c)" was not a valid option, why didn't people just use "Copyright"? "Copyright 2014" sounds unambigious, has no redundancy, looks good, uses no non-ASCII characters ... so why is "Copyright (c) 2014" so often prefered?

@leofidus No clue, though a lot of legalese stuff is cargo cult. Better to be on the safe side in case something goes to court, even if that implies adding three of four (C) and TM symbols :-)

Actually isn't wrong as well to change all files to 2014, since the file is fundamental part of the entire project and the project was modified. The companies where I worked was used to change all copyright files (actually this could be automatic). It's just a convention of this project, and it's also ok! :)

Please don't bikeshed this, we did that last year. Official Policy is to change the copyright year on the file if the file is changed in that year. Closing this pull request as Against Official Policy.