From d17aaf94d5a7d399c50ef2431aaeb24e84d499d9 Mon Sep 17 00:00:00 2001
From: Glen Barber
Date: Tue, 25 Oct 2016 16:44:27 +0000
Subject: [PATCH] Make igor(1) less unhappy about security.xml. Translators can
ignore, this is whitespace-only.
Sponsored by: The FreeBSD Foundation
---
en_US.ISO8859-1/htdocs/security/security.xml | 42 ++++++++++----------
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/en_US.ISO8859-1/htdocs/security/security.xml b/en_US.ISO8859-1/htdocs/security/security.xml
index 57c84b6bcf..44b8430edd 100644
--- a/en_US.ISO8859-1/htdocs/security/security.xml
+++ b/en_US.ISO8859-1/htdocs/security/security.xml
@@ -89,19 +89,19 @@
which is primarily oriented towards &os; developers.)
- The -STABLE branch tags have
- names like stable/10. The corresponding builds have
- names like FreeBSD 10.1-STABLE.
+ The -STABLE branch tags have names like stable/10.
+ The corresponding builds have names like FreeBSD
+ 10.1-STABLE.
Each FreeBSD Release has an associated Security Branch.
- The Security Branch tags have names like releng/10.1.
+ The Security Branch tags have names like releng/10.1.
The corresponding builds have names like FreeBSD
10.1-RELEASE-p4.
- Issues affecting the FreeBSD Ports Collection are covered separately in the FreeBSD VuXML
- document.
+ Issues affecting the FreeBSD Ports Collection are covered
+ separately in the FreeBSD
+ VuXML document.
How to update your system
@@ -210,8 +210,8 @@
- In the run-up to a release, a number of -BETA
- and -RC releases may be published for testing purposes. These releases are only
+
In the run-up to a release, a number of -BETA and -RC releases
+ may be published for testing purposes. These releases are only
supported for a few weeks, as resources permit, and will not be
listed as supported on this page. Users are strongly discouraged
from running these releases on production systems.
@@ -229,9 +229,9 @@
release.
The details and rationale behind this change can be found in the
- official
- announcement sent in February 2015.
+ official
+ announcement sent in February 2015.
Previously, branches were designated as either Normal or
Extended. The designation was used as a guideline for
@@ -240,18 +240,18 @@
- Normal
- Releases which are published from a -STABLE branch were
- supported by the Security Officer for a minimum of 12 months after the
- release, and for sufficient additional time (if needed) to ensure
- that there is a newer release for at least 3 months before the
- older Normal release expires.
+ supported by the Security Officer for a minimum of 12 months
+ after the release, and for sufficient additional time (if
+ needed) to ensure that there is a newer release for at least
+ 3 months before the older Normal release expires.
- Extended
- Selected releases (normally every second release plus the last
- release from each -STABLE branch) were supported by the
- Security Officer for a minimum of 24 months after the release,
- and for sufficient additional time (if needed) to ensure that
- there is a newer Extended release for at least 3 months before the
- older Extended release expires.
+ release from each -STABLE branch) were supported by the Security
+ Officer for a minimum of 24 months after the release, and for
+ sufficient additional time (if needed) to ensure that there is
+ a newer Extended release for at least 3 months before the older
+ Extended release expires.