reported content now uses new core language strings
thewire now uses new core language strings
uservalidationbyemail now uses new core language strings
logrotate now uses new core language strings
blog now uses new core language strings
bookmarks now uses new core language strings
diagnostics now uses new core language strings
file now uses new core language strings
embed language string no longer used
groups now uses new core language strings
use a core language string for no results
members now uses new core language strings
messages now uses new core language strings
use generic sort language strings
Update CacheHandler.php

This line looks suspicious. Shouldn't the `$request_var` start with a `/` ?
If I have `/cache/0/default/css/admin`, I'd rather have
  `$request_var = "/0/default/css/admin";`
than 
  `$request_var = "0/default/css/admin";`

I don't know how it works with Apache and others, but with Nginx, it simplifies things. Therefore:

  `if (!preg_match('#^/?([0-9]+)/([^/]+)/(.+)$#', $request_var, $matches)) {`

(drop the `?` if that is not needed)
Add test to allow leading slash in the cache URL regex
Merge pull request #5974 from hellekin/patch-1

Update CacheHandler.php
Merge pull request #5910 from jdalsem/use-new-translation-strings

Eases translation via more generic strings
Make files non-executable
Fixes #6012. Getting correct client IP behind proxy.