Legally incredibly dubious, particularly since we don't follow it
strictly as policy, and we have git history instead, which does it right.
This is just a waste of time and a cargo cult.

Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>

Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>

Some day I will remember which is which on string styles.

Signed-off-by: Noah Kantrowitz <noah@coderanger.net>

Signed-off-by: Noah Kantrowitz <noah@coderanger.net>

Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"

Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"

This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.

If we don't defensively program here, the result is terrible.  All that
gets raised is "negative argument" from deep within the formatter and
from then on the formatter is broken.  It will continue to raise errors
from events called from inside the Chef::Client exception handler and
you're gonna have a bad time.