On Wed, 20 Jan 2016, Jakub Jelinek wrote: >> Content-Security-Policy: default-src 'self' http: https: >> >> So either we get the configuration of the web server changed, or >> indeed we need to touch all those existing pages. > At least the warning/error/note styles are something that multiple pages > are using and going to use in the future, so if that could be defined in > the main gcc.css, it would be enough.
Done thusly. With this change, at least gcc-6/changes.html should be fine again. And I can commit working my way backwards through all the other changes.html pages over the coming couple of days. Gerald Move the boldred class from gcc-6/changes.html to gcc.css. Introduce boldcyan and boldmagenta classes and use them in gcc-6/changes.html. Index: gcc.css =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc.css,v retrieving revision 1.25 diff -u -r1.25 gcc.css --- gcc.css 12 Sep 2011 09:42:59 -0000 1.25 +++ gcc.css 20 Jan 2016 17:26:10 -0000 @@ -49,7 +49,11 @@ border-width: thin; padding: 4px; } - + +.boldcyan { font-weight:bold; color:cyan; } +.boldmagenta { font-weight:bold; color:magenta; } +.boldred { font-weight:bold; color:red; } + /* Classpath versus libgcj merge status page. */ .classpath-only { background-color: #FFFFAA; } Index: gcc-6/changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/changes.html,v retrieving revision 1.49 diff -u -r1.49 changes.html --- gcc-6/changes.html 19 Jan 2016 22:42:16 -0000 1.49 +++ gcc-6/changes.html 20 Jan 2016 17:26:10 -0000 @@ -3,11 +3,6 @@ <head> <title>GCC 6 Release Series — Changes, New Features, and Fixes</title> -<style type="text/css"> - .boldred { font-weight:bold; color:red; } -</style> - <!-- GCC maintainers, please do not hesitate to update/contribute entries concerning those part of GCC you maintain! 2002-03-23, Gerald. --> @@ -80,9 +75,9 @@ In addition, there is now initial support for precise diagnostic locations within strings: <blockquote><pre> -<b>format-strings.c:3:14:</b> <b style='color:magenta'>warning:</b> field width specifier <b>'*'</b> expects a matching <b>'int'</b> argument [<b style='color:magenta'>-Wformat=</b>] +<b>format-strings.c:3:14:</b> <span class="boldmagenta">warning:</span> field width specifier <b>'*'</b> expects a matching <b>'int'</b> argument [<span class="boldmagenta">-Wformat=</span>] printf("%*d"); - <b style='color:magenta'>^</b> + <span class="boldmagenta">^</span> </pre></blockquote></li> <li>Diagnostics can now contain "fix-it hints", which are displayed in context underneath the relevant source code. For example: @@ -126,12 +121,12 @@ <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1266">CVE-2014-1266</a>: <blockquote><pre> <b>sslKeyExchange.c:</b> In function <b>'SSLVerifySignedServerKeyExchange'</b>: -<b>sslKeyExchange.c:631:8:</b> <b style='color:magenta'>warning:</b> statement is indented as if it were guarded by... [<b style='color:magenta'>-Wmisleading-indentation</b>] - <b style='color:magenta'>goto</b> fail; - <b style='color:magenta'>^~~~</b> -<b>sslKeyExchange.c:629:4:</b> <b style='color:cyan'>note:</b> ...this 'if' clause, but it is not - <b style='color:cyan'>if</b> ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) - <b style='color:cyan'>^~</b> +<b>sslKeyExchange.c:631:8:</b> <span class="boldmagenta">warning:</span> statement is indented as if it were guarded by... [<span class="boldmagenta">-Wmisleading-indentation</span>] + <span class="boldmagenta">goto</span> fail; + <span class="boldmagenta">^~~~</span> +<b>sslKeyExchange.c:629:4:</b> <span class="boldcyan">note:</span> ...this 'if' clause, but it is not + <span class="boldcyan">if</span> ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) + <span class="boldcyan">^~</span> </pre></blockquote> This warning is enabled by <code>-Wall</code>.</li> </ul>