From: Eric Wong <e@80x24.org>
To: yahns-public@yhbt.net
Subject: [PUSHED] frozen_string_literal and copyright updates
Date: Sat, 2 Jan 2016 22:47:37 +0000 [thread overview]
Message-ID: <20160102224737.GA787@dcvr.yhbt.net> (raw)
Two giant tree-wide changes pushed to master, if you have questions or
comments, reply with the commit subject line so the search engines can
find it:
enable frozen_string_literal for Ruby 2.3+
copyright updates for 2016
93 files changed, 337 insertions(+), 253 deletions(-)
Also, the cgit instance @ http://yhbt.net/yahns.git/ will soon be
replaced with something friendlier to non-CSS users (and with
better mail integration to boot).
http://yhbt.net/yahns.git/patch?id=ddea1b7e04b7e3475bb615c35e2156c9626b4eac
http://yhbt.net/yahns.git/commit?id=ddea1b7e04b7e3475bb615c35e2156c9626b4eac
copyright updates for 2016
Using the 'update-copyright' script from gnulib[1]:
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \
UPDATE_COPYRIGHT_USE_INTERVALS=2 \
xargs /path/to/gnulib/build-aux/update-copyright
We're also switching to 'GPL-3.0+' as recommended by SPDX
to be consistent with our gemspec and other metadata
(as opposed to the longer but equivalent "GPLv3 or later").
[1] git://git.savannah.gnu.org/gnulib.git
http://yhbt.net/yahns.git/patch?id=9e24bae3428f726800da2963a8f2695f7d4064cd
http://yhbt.net/yahns.git/commit?id=9e24bae3428f726800da2963a8f2695f7d4064cd
enable frozen_string_literal for Ruby 2.3+
There are likely yet-to-be-discovered bugs in here.
Also, keeping explicit #freeze calls for 2.2 users, since most
users have not migrated to 2.3, yet.
--
EW
next reply other threads:[~2016-01-02 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 22:47 Eric Wong [this message]
2016-01-04 12:06 ` [PUSHED] frozen_string_literal and copyright updates Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/yahns/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160102224737.GA787@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=yahns-public@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/yahns.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).