From 11a4a7b667b541fc070c1a4d0d85bca574cd4bbe Mon Sep 17 00:00:00 2001
From: "W. Eric Norum" <wenorum@lbl.gov>
Date: Mon, 21 Jul 2008 17:44:12 +0000
Subject: [PATCH] Fix placement.

---
 documentation/RELEASE_NOTES.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/documentation/RELEASE_NOTES.html b/documentation/RELEASE_NOTES.html
index dd5836d3a..27b3cc6be 100644
--- a/documentation/RELEASE_NOTES.html
+++ b/documentation/RELEASE_NOTES.html
@@ -18,6 +18,10 @@
 IOC's console by the errlog subsystem are sent to the stderr output stream
 rather than to stdout.</p>
 
+<h4>ipToAsciiProxy</h4>
+
+<p>This thread calls upon vendor libraries which may use significant amounts of stack.  Account for this by providing the ipToAsciiProxy thread with an epicsThreadStackBig stack.</p>
+
 <h4>iocBuild, iocRun and iocPause</h4>
 
 <p>These three new commands are mainly intended for use with DESY's redundant
@@ -30,10 +34,6 @@ either <tt>iocInit</tt> or <tt>iocBuild</tt> + <tt>iocRun</tt>) the
 stopping all scan activity.  The <tt>iocRun</tt> command restarts the IOC from
 this state.</p>
 
-<h4>ipToAsciiProxy</h4>
-
-<p>This thread calls upon vendor libraries which may use significant amounts of stack.  Account for this by providing the ipToAsciiProxy thread with an epicsThreadStackBig stack.</p>
-
 <p>While this might seem like a useful thing to be able to do, we have not
 tested it on IOCs using real-world I/O, and it is not unlikely that pausing an
 operational IOC could cause irremdial havok to any device support, sequence