You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Look at the source code
What is the expected output? What do you see instead?
Given the datestamp in the filename, I would assume that the copyright
notice would be dated 2008 instead of 2006.
Note that the JavaScript file hasn't got any copyright notice at all.
What version of the product are you using? On what operating system?
diff_match_patch_20080426.zip
Please provide any additional information below.
This is obviously a purely cosmetic issue.
Original issue reported on code.google.com by hale.o.k...@gmail.com on 29 Apr 2008 at 7:56
The text was updated successfully, but these errors were encountered:
That's a good question. Google's policy for source code is to record the year
of
each file's creation, then leave the date unchanged when making updates. This
is the
most conservative approach, allowing the copyright to expire sooner.
Some companies increment the copyright every year in order to maintain a claim
for
perpetual copyright. Other companies maintain a date range for each file,
though
this can get complicated:
http://www.nntp.perl.org/group/perl.perl5.porters/2003/03/msg72648.html
Original comment by neil.fra...@gmail.com on 11 May 2008 at 3:30
Original issue reported on code.google.com by
hale.o.k...@gmail.com
on 29 Apr 2008 at 7:56The text was updated successfully, but these errors were encountered: