I noticed lots of trailing whitespace in one of cmd/trace's HTML files.
While at it, remove a few others from still-maintained files. Leave old
documents alone, such as doc/devel/weekly.html.
Change-Id: I7de7bbb6dd3fe6403bbb1f1178a8d3640c1e537b
Reviewed-on: https://go-review.googlesource.com/c/go/+/196178
Run-TryBot: Daniel Martí <mvdan@mvdan.cc>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
<p>
First, add <code>"regexp"</code> to the <code>import</code> list.
-Then we can create a global variable to store our validation
+Then we can create a global variable to store our validation
expression:
</p>
<p>
Changes to the Go frontend should follow the same process as for the
main Go repository, only for the <code>gofrontend</code> project and
-the <code>gofrontend-dev@googlegroups.com</code> mailing list
+the <code>gofrontend-dev@googlegroups.com</code> mailing list
rather than the <code>go</code> project and the
<code>golang-dev@googlegroups.com</code> mailing list. Those changes
will then be merged into the GCC sources.
<p>
If you cannot use a release, or prefer to build gccgo for
-yourself,
+yourself,
the gccgo source code is accessible via Subversion. The
GCC web site
has <a href="https://gcc.gnu.org/svn.html">instructions for getting the
<p>
These considerations led to
-<a href="https://commandcenter.blogspot.com/2017/09/go-ten-years-and-climbing.html">a
+<a href="https://commandcenter.blogspot.com/2017/09/go-ten-years-and-climbing.html">a
series of discussions</a> from which Go arose, first as a set of ideas and
desiderata, then as a language.
An overarching goal was that Go do more to help the working programmer
<p>
Companies often permit outgoing traffic only on the standard TCP ports 80 (HTTP)
-and 443 (HTTPS), blocking outgoing traffic on other ports, including TCP port 9418
+and 443 (HTTPS), blocking outgoing traffic on other ports, including TCP port 9418
(git) and TCP port 22 (SSH).
When using HTTPS instead of HTTP, <code>git</code> enforces certificate validation by
default, providing protection against man-in-the-middle, eavesdropping and tampering attacks.
<span id="content"></span>
<span id="significance">
-
+
<svg id="insignificant" viewBox="0 0 128 128">
<circle cx="64" cy="64" r="60"></circle>
<circle cx="44" cy="44" r="4"></circle>
<line x1="36" x2="92" y1="80" y2="80"></line>
</svg>
-
+
<svg id="significantly_better" viewBox="0 0 128 128">
<circle cx="64" cy="64" r="60"></circle>
<circle cx="44" cy="44" r="4"></circle>
<path d="M 28 64 Q 64 128 100 64"></path>
</svg>
-
+
<svg id="significantly_worse" viewBox="0 0 128 128">
<circle cx="64" cy="64" r="60"></circle>
<circle cx="44" cy="44" r="4"></circle>
<div id="header"></div>
<input id="stacking-distance-slider" max="400" min="1" step="1" type="range"/>
-
+
<canvas id="canvas"></canvas>
<img id="chrome-left"/>
<img id="chrome-mid"/>
<label id="label"></label>
</template>
</dom-module><template id="chart-base-template">
- <svg>
+ <svg>
<g id="chart-area" xmlns="http://www.w3.org/2000/svg">
<g class="x axis"></g>
<g class="y axis"></g>
<div id="label">Heap details</div>
<div id="view_mode_container">
<span>View mode:</span>
-
+
</div>
</div>
<div id="contents">
font-size: 15px;
}
</style>
-
+
<div id="label"></div>
<div id="aggregation_mode_container">
<span>Metric aggregation:</span>
-
+
</div>
</template>
</dom-module><dom-module id="tr-ui-a-stacked-pane-view">
</style>
<tr-ui-b-table id="table">
</tr-ui-b-table>
-
+
</template>
</dom-module><dom-module id="tr-ui-a-selection-summary-table">
<template>
</style>
<tr-ui-b-table id="table">
</tr-ui-b-table>
-
+
</template>
</dom-module><dom-module id="tr-ui-b-radio-picker">
<template>