Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Feb 2016 04:40:08 +0000 (UTC)
From:      Benjamin Kaduk <bjk@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r48139 - head/en_US.ISO8859-1/htdocs/news/status
Message-ID:  <201602020440.u124e8SC061589@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: bjk
Date: Tue Feb  2 04:40:07 2016
New Revision: 48139
URL: https://svnweb.freebsd.org/changeset/doc/48139

Log:
  Finish up my editing pass
  
  Among other things, use just "head" to talk about the development
  branch, not "HEAD".

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml	Mon Feb  1 16:26:55 2016	(r48138)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-10-2015-12.xml	Tue Feb  2 04:40:07 2016	(r48139)
@@ -169,8 +169,9 @@
     </contact>
 
     <links>
-      <url href="https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html">Bruce's email requesting bool be added to <tt>style(9)</tt></url>
-      <url href="https://reviews.FreeBSD.org/D4384">Differential Revision for the change</url>
+      <url
+href="https://lists.FreeBSD.org/pipermail/svn-src-head/2015-December/079671.html">Bruce's Email Requesting <tt>bool</tt> be Added to <tt>style(9)</tt></url>
+      <url href="https://reviews.FreeBSD.org/D4384">Differential Revision for the Change</url>
     </links>
 
     <body>
@@ -366,7 +367,7 @@
 
     <links>
       <url href="https://wiki.FreeBSD.org/FreeBSD/arm/Odroid-C1">&os; on Odroid-C1</url>
-      <url href="https://svnweb.FreeBSD.org/changeset/base/291683">Commit adding glue driver</url>
+      <url href="https://svnweb.FreeBSD.org/changeset/base/291683">Commit Adding Glue Driver</url>
     </links>
 
     <body>
@@ -465,7 +466,7 @@
     </contact>
 
     <links>
-      <url href="https://github.com/bsdjhb/gdb/tree/FreeBSD-threads">New 1:1-only thread target for &os;</url>
+      <url href="https://github.com/bsdjhb/gdb/tree/FreeBSD-threads">New 1:1-Only Thread Target for &os;</url>
     </links>
 
     <body>
@@ -473,7 +474,7 @@
 	<tt>devel/gdb</tt> port.</p>
 
       <p>Changes to support cross-debugging of crashdumps in libkvm
-	were committed to HEAD in r291406.</p>
+	were committed to head in r291406.</p>
 
       <p>A new thread target for &os; that is suitable for merging
 	upstream has been written and lightly tested.  However, it is
@@ -571,7 +572,7 @@
     <links>
       <url href="http://kernelnomicon.org/?p=534">Beaglebone Black with 4DCAPE-43T Demo</url>
       <url href="https://wiki.FreeBSD.org/201510DevSummit/GraphicsStack">Input Stack Plans</url>
-      <url href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens">evdev Port</url>
+      <url href="https://wiki.FreeBSD.org/SummerOfCode2014/evdev_Touchscreens"><tt>evdev</tt>; Port</url>
     </links>
 
     <body>
@@ -582,13 +583,13 @@
       <p>Proper touchscreen support would consist of a userland event
 	reading API, a kernel event reporting API, and kernel hardware
 	drivers for specific devices.  There is an ongoing effort to
-	port the Linux evdev API to &os; so applications that use
+	port the Linux <tt>evdev</tt> API to &os; so applications that use
 	libraries like libinput or tslib could be used without any
 	major changes.  Since it is not yet complete, I created a
-	naive evdev-like API for both kernel and tslib and was able to
+	naive <tt>evdev</tt>-like API for both kernel and tslib and was able to
 	run a demo on a Beaglebone Black with 4DCAPE-43T.</p>
 
-      <p>Once evdev makes it into the tree, both hardware drivers
+      <p>Once <tt>evdev</tt> makes it into the tree, both hardware drivers
 	can be modified to include &quot;report events&quot;
 	portions and committed.</p>
     </body>
@@ -1083,9 +1084,9 @@
 
     <links>
       <url href="https://github.com/FreeBSD/pytoport">pytoport: Generate &os; Ports from Python modules on PyPI</url>
-      <url href="https://github.com/bbqsrc/bandar">bandar: Create Development Overlays for the Ports tree</url>
+      <url href="https://github.com/bbqsrc/bandar">bandar: Create Development Overlays for the Ports Tree</url>
       <url href="https://github.com/bbqsrc/skog-python">skog: Generate Visual Dependency Trees for &os; Ports</url>
-      <url href="https://github.com/bbqsrc/spdx-lookup-python">spdx-lookup: SPDX License List Query Tool</url>
+      <url href="https://github.com/bbqsrc/spdx-lookup-python"><tt>spdx-lookup</tt>: SPDX License List Query Tool</url>
     </links>
 
     <body>
@@ -1117,7 +1118,7 @@
 	in git and the larger upstream SVN tree I was using in
 	poudriere.  I built a tool called <tt>bandar</tt> that takes
 	advantage of the FUSE version of unionfs to easily overlay my
-	dev tree on the upstream tree, run linting, poudriere, and
+	dev tree on the upstream tree, run lint checks, poudriere, and
 	generate archives with ease.</p>
 
       <p>I am very impressed with how easy it was to build more
@@ -1227,7 +1228,7 @@
 	eliminates the effect of selecting small unrelated processes
 	for OOM kill.</p>
 
-      <p>The rewrite was committed to HEAD in r290917 and r290920.</p>
+      <p>The rewrite was committed to head in r290917 and r290920.</p>
     </body>
 
     <sponsor>The FreeBSD Foundation</sponsor>
@@ -1253,7 +1254,7 @@
     <body>
       <p>A new driver, <tt>cxgbei</tt>, enabling hardware accelerated
 	iSCSI with Chelsio's T5- and T4-based offload-capable cards,
-	has been committed to HEAD.  Both Initiator and Target are
+	has been committed to head.  Both Initiator and Target are
 	supported.  The wire traffic is standard iSCSI (SCSI over TCP
 	as per RFC 3720, etc.) so an Initiator/Target using this
 	driver will interoperate with all other standards-compliant
@@ -1338,7 +1339,7 @@
 	features various bug fixes and documentation improvements; the
 	complete list of changes is documented in the
 	<a href="https://github.com/openbsm/openbsm/blob/master/NEWS">NEWS</a>;
-	file on GitHub.  The release was imported into &os; HEAD and
+	file on GitHub.  The release was imported into &os; head and
 	merged to &os; 10-STABLE.  As such, it will be part of &os;
 	10.3-RELEASE.</p>
     </body>
@@ -1434,7 +1435,7 @@
       </ul>
 
       <p>The port is under community review and will be integrated
-	into HEAD soon.</p>
+	into head soon.</p>
     </body>
 
     <sponsor>
@@ -1467,7 +1468,7 @@
     </contact>
 
     <links>
-      <url href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468">PR for the new Port</url>
+      <url href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468">PR for the New Port</url>
       <url href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-FreeBSD.md">Installation Guide</url>
       <url href="https://github.com/gitlabhq/gitlabhq/">Upstream GitLab website</url>
     </links>
@@ -1530,7 +1531,8 @@
     <body>
       <p>There are more and more machines on the internet that
 	<strong>only</strong> support IPv6.  I manage some of them,
-	and was regularly hit by missing IPv6 support when building
+	and was regularly hit by missing IPv6 support when
+	fetching the distfiles needed for building
 	ports.</p>
 
       <p>I did some research into the impact of missing IPv6 support
@@ -1562,8 +1564,8 @@
     </contact>
 
     <links>
-      <url href="https://FreeBSD.kde.org/">KDE on &os; website</url>
-      <url href="https://FreeBSD.kde.org/area51.php">Experimental KDE ports staging area</url>
+      <url href="https://FreeBSD.kde.org/">KDE on &os; Website</url>
+      <url href="https://FreeBSD.kde.org/area51.php">Experimental KDE Ports Staging Area</url>
       <url href="https://wiki.FreeBSD.org/KDE">KDE on &os; Wiki</url>
       <url href="https://mail.kde.org/mailman/listinfo/kde-FreeBSD">KDE/&os; Mailing List</url>
       <url href="http://src.mouf.net/area51/log/branches/plasma5">Development Repository for Integrating KDE Frameworks 5 and Plasma 5</url>
@@ -2537,7 +2539,7 @@
 	  yet sent to upstream).</li>
       </ul>
 
-      <p>Most of the introduced changes have been committed to HEAD
+      <p>Most of the introduced changes have been committed to head
 	and more are on the way.</p>
     </body>
 
@@ -3133,8 +3135,8 @@
 	<li>Konstantin rewrote the out of memory killer logic, which,
 	  in particular, fixed &os; operation on systems without swap,
 	  especially systems with very little memory.  The latter are
-	  becoming more and more common with popularity of embedded
-	  ARM platforms were &os; runs, but it also affects large
+	  becoming more and more common with the popularity of embedded
+	  ARM platforms where &os; runs, but it also affects large
 	  systems which are usually configured without swap.  He also
 	  finalized and committed the shared page support for the
 	  ARMv7 and ARMv8 systems.  This allows for a non-executable
@@ -3189,7 +3191,7 @@
 	    <tt>CUBIEBOARD</tt>, and <tt>CUBIEBOARD2</tt> arm
 	    images.</li>
 
-	  <li>Deprecated use of MD5 checksums used for verifying
+	  <li>Deprecated the use of MD5 checksums for verifying
 	    installation media downloaded from the &os; Project
 	    mirrors.</li>
 
@@ -3257,7 +3259,7 @@
 	support for &os; on x86 as a guest was introduced in version
 	8, and ARM support is currently being worked on.  Support for
 	running &os; as an amd64 Xen host (Dom0) is available in
-	HEAD.</p>
+	head.</p>
 
       <p>The x86 work done during this quarter has been focused on
 	rewriting the PVH implementation inside of Xen, into what is
@@ -3364,7 +3366,7 @@
 	directly accessing the timer register.  This reduces the
 	overhead of these calls as we no longer need to call into the
 	kernel.  This also moves the signal trampoline code away from
-	the stack allowing for the stack to become non-executable.</p>
+	the stack, allowing for the stack to become non-executable.</p>
 
       <p>CloudABI support for arm64 was added.  This included moving
 	the machine-independent code into a separate file to be shared
@@ -3378,7 +3380,7 @@
 	arm64 have been fixed, resulting in over 17,000 ports building
 	for the architecture.</p>
 
-      <p>The machine-dependent portions of kernel support for
+      <p>The machine-dependent portion of kernel support for
 	single-stepping userland binaries has been started.  This will
 	allow debuggers like <tt>lldb</tt> to step through an
 	application while debugging.</p>
@@ -3814,7 +3816,7 @@
 	is activated to continue transmission.</p>
 
       <p>Additional features of the new <tt>sendfile</tt> are new
-	flags that provide an application with extra control over the
+	flags that provide the application with extra control over the
 	transmitted content.  Now it is possible to prevent caching of
 	content in memory, which is useful when it is known that the
 	content is unlikely to be reused any time soon.  In such
@@ -3833,8 +3835,8 @@
 	idea of such an asynchronous drop-in replacement was discussed
 	amongst &a.glebius;, &a.scottl;, &a.kib;, &a.adrian;, and Igor
 	Sysoev.  The initial prototype was coded by Gleb under the
-	supervision of Kostik on the VM parts of patch, and under
-	constant pressure from Igor, who demanded that nginx be
+	supervision of Kostik on the VM parts of the patch, and under
+	constant pressure from Igor, who demanded that <tt>nginx</tt> be
 	capable of running with the new <tt>sendfile(2)</tt> with no
 	modifications.  The prototype demonstrated good performance
 	and stability and quickly went into Netflix production in late
@@ -3960,7 +3962,7 @@
     </contact>
 
     <body>
-      <p>The NanoBSD updates target three main areas.  First,
+      <p>This quarter's NanoBSD updates target three main areas.  First,
 	building a NanoBSD image required root privileges.  Second,
 	building for embedded platforms required detailed knowledge of
 	the format required to boot.  Third, the exact image sizes
@@ -3968,7 +3970,7 @@
 
       <p>When NanoBSD was written, &os;'s build system required root
 	privileges for the install step and onward.  NanoBSD added to
-	this by creating a <tt>md(4)</tt> device to construct the
+	this by creating a <tt>md(4)</tt> device in which to construct the
 	image.  Some configurations of NanoBSD added further to this
 	by creating a chroot in which to cleanly build packages.
 	NanoBSD solves the first problem using the new
@@ -4438,7 +4440,7 @@
     </contact>
 
     <links>
-      <url href="https://hardenedbsd.org/" />
+      <url href="https://hardenedbsd.org/">HardenedBSD Website</url>
       <url href="https://hardenedbsd.org/article/shawn-webb/2015-12-31/introducing-hardenedbsds-new-binary-updater">Introducing HardenedBSD's New Binary Updater</url>
       <url href="https://hardenedbsd.org/article/shawn-webb/2015-11-22/introducing-secadm-030-beta-01"><tt>secadm</tt>; Beta Published</url>
       <url href="https://hardenedbsd.org/article/admin/2015-11-22/new-package-building-server">New Package Building Server</url>
@@ -4455,7 +4457,7 @@
 	refactored, but lib32 is now disabled by default.</p>
 
       <p>We have developed a new binary update utility,
-	<tt>hbsd-update</tt> akin to <tt>freebsd-update</tt>.  In
+	<tt>hbsd-update</tt>, akin to <tt>freebsd-update</tt>.  In
 	addition to normal OS installs, it can also update jails and
 	ZFS Boot Environments (ZFS BEs).  Updates are signed using
 	X.509 certificates.</p>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201602020440.u124e8SC061589>