svn commit: r45276 - head/en_US.ISO8859-1/htdocs/news/status

[Glen Barber]

Author: gjb
Date: Sun Jul 13 23:12:16 2014
New Revision: 45276
URL: http://svnweb.freebsd.org/changeset/doc/45276

Log:
  Whitespace cleanup, no content changes.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml	Sun Jul 13 23:09:42 2014	(r45275)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-04-2014-06.xml	Sun Jul 13 23:12:16 2014	(r45276)
@@ -422,21 +422,25 @@
     </body>
 
     <help>
-      <task>
-           PPC on AMD64 emulation.  WIP as there appears to be some serious issues running the bsd-user binary on big endian hardware.  Justin Hibbits working on this.
-      </task>
-      <task>
-           SPARC64 on AMD64 emulation is non-functional and instantly segfaults.  Looking for someone to poke at the bits here.
-      </task>
-      <task>
-           External Tool Chain, XDEV support.  Partial support for using an AMD64 tool chain that can output other architecture (use AMD64 toolchain to build MIPS64 packages).  Currently tracking a linking issue with ports-mgmt/pkg.  Thanks to Warner Losh, Baptiste Daroussin, Dimitry Andric for poking at bits in here to make the XDEV target useful.
-      </task>
-      <task>
-           Signal Handling, MIPS/ARMV6 target still displays a failure that manifests itself when building devel/p5-Sys-SigAction
-      </task>
-      <task>
-           Massive documentation update needed.  These modifications actually allow you to chroot into a MIPS or ARMv6 environment and use native tool chains and libraries to prototype your software for a target platform.
-      </task>
+      <task>PPC on AMD64 emulation.  WIP as there appears to be some
+	serious issues running the bsd-user binary on big endian
+	hardware.  Justin Hibbits working on this.</task>
+      <task>SPARC64 on AMD64 emulation is non-functional and instantly
+	segfaults.  Looking for someone to poke at the bits
+	here.</task>
+      <task>External Tool Chain, XDEV support.  Partial support for
+	using an AMD64 tool chain that can output other architecture
+	(use AMD64 toolchain to build MIPS64 packages).  Currently
+	tracking a linking issue with ports-mgmt/pkg.  Thanks to
+	Warner Losh, Baptiste Daroussin, Dimitry Andric for poking at
+	bits in here to make the XDEV target useful.</task>
+      <task>Signal Handling, MIPS/ARMV6 target still displays
+	a failure that manifests itself when building
+	devel/p5-Sys-SigAction.</task>
+      <task>Massive documentation update needed.  These modifications
+	actually allow you to chroot into a MIPS or ARMv6 environment
+	and use native tool chains and libraries to prototype your
+	software for a target platform.</task>
     </help>
   </project>
 
@@ -492,12 +496,18 @@
 
     <help>
       <task>Migrate bsd.python.mk to the Uses framework.</task>
-      <task>Develop a high-level and lightweight Python Ports Policy.</task>
-      <task>Add support for granular dependencies (for example >=1.0,<2.0).</task>
-      <task>See what adding pip (Python Package Index) support will require.</task>
-      <task>Add default QA targets and functions for Python ports (TEST_DEPENDS, regression-test, etc.)</task>
-      <task>More tasks can be found on the team's wiki page (see links).</task>
-      <task>To get involved, interested people can say hello on IRC and let us know their areas of interest!</task>
+      <task>Develop a high-level and lightweight Python Ports
+	Policy.</task>
+      <task>Add support for granular dependencies (for example
+	>=1.0,<2.0).</task>
+      <task>See what adding pip (Python Package Index) support will
+	require.</task>
+      <task>Add default QA targets and functions for Python ports
+	(TEST_DEPENDS, regression-test, etc.)</task>
+      <task>More tasks can be found on the team's wiki page (see
+	links).</task>
+      <task>To get involved, interested people can say hello on IRC
+	and let us know their areas of interest!</task>
     </help>
   </project>