Upgrading to a new version of the SDK

[RayFoulkes]

More of a plea than a problem. When I migrate to a new version of the SDK I try to be very careful. So, I use sha256sum to check all similarly named files from one version to another. I was aghast to discover that there are NO files unchanged.  Here is the major culprit:

* Copyright (c) 2009 - 2018, Nordic Semiconductor ASA

versus

 * Copyright (c) 2009 - 2019, Nordic Semiconductor ASA

with, in many cases, no other change.

Now I know that laws and lawyers are some of the most illogical constructs on earth, but can someone persuade them to find a means of claiming copyright that doesn't totally screw up configuration control systems like GIT to which ANY change is a new version, including the copyright statement. Files that have no change should have the same sha256 sum.

IANAL but why put a terminating year in a copyright claim in the first place?

Sorry a bit of a rant, I know all I have to do is script an edit to remove the copyright statement prior to sha calculation - but sigh, haven't we all enough to do?

[Duy]

I think this link can help you. 

For my experience, I don't use any tool except Beyond Compare to update the SDK 'cause I can understand and manage my customization.

Best regards,

    Duy

[RayFoulkes]

Sorry, I have access to compare tools (various) including Ultracompare, Kompare and the venerable cmp. I should have said what I was doing was to script the detection of any differences in bash of hundreds of files prior to implementing (for example) automatic patches. I really was trying to avoid eyeballing every comparison to check if the differences are significant. I guess the lockdown was getting to me, after all I have only to use

sed '/Copyright (c)/'d filename | sha256sum

to strip out the offending line. Sorry to be rather trivial, maybe just close and forget this rant....