With updated langpacks
… to linux-image-3.12-0.bpo.1-486 linux-image-3.12-0.bpo.1-686-pae
…ng intel-ucode ... error
…efault value like normal. Non-English HTTP accept language header should work properly now, so DDG searches should be localised et al. Hat tip: Mike Kaply
This option wasn't actually used in practice and now that the fetches are always shallow, there is no longer any guarantee that any commit, apart from the fetched tip, is actually available, so the option is really no longer useful.
When upgrading, we really only need the most recent commit, not all the commits between our current version and the new one. By passing --depth=1 to git fetch, we'll get just that (though there is a bug in current versions of git that will give 2 revisions instead of 1, but that will be fixed in a future version). This saves bandwidth when downloading (git is still smart enough to not download any objects it already has, even if it does not explicitely know that the new and old revisions are related).
Previously, only one of these options would be processed and copied to the commandline. Since you cannot add spaces inside the boot_append option, you could only specify one commandline option in this way. By simply processing all boot_append options, you can specify a separate boot_append option for each commandline option that should end up on the commandline.
Before, it would stop as soon as it found a value. However, this would mean that it's impossible to override a value by specifying it again later (in particular, values from the server-side config would _not_ override values from the commandline, which seems wanted). A few other places process commandline options without using cmdline_get, but they loop over $(cmdline) and switch on each value. These places would see all matching values instead of just the first one (and usually only the last one would have effect). This commit lets cmdline_get match that behaviour, so it makes things more consistent.
…moji.ttf, fixes #178
Merge commit '9d8b326ebca9dc80316e468855b594c5490b12f8'
https://www.adobe.com/support/security/bulletins/apsb13-21.html Priority 3 - This update resolves vulnerabilities in a product that has historically not been a target for attackers. Adobe recommends administrators install the update at their discretion.
… the UI would be disruptive. http://webconverger.org/img/mixed-content-warning.png http://www.mozilla.org/en-US/firefox/23.0.1/releasenotes/