From 597b93798a804cde1783d6d2ab53b348d57c44cd Mon Sep 17 00:00:00 2001
From: Tom Rondeau <tom@trondeau.com>
Date: Mon, 7 Jul 2014 12:18:00 -0400
Subject: Removing trailing/extra whitespaces before release.

We should be more careful about letting these into the code in the future. In emacs, we can use (add-hook 'before-save-hook 'delete-trailing-whitespace).
---
 docs/doxygen/other/logger.dox          | 4 ++--
 docs/doxygen/other/msg_passing.dox     | 4 ++--
 docs/doxygen/other/thread_affinity.dox | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

(limited to 'docs/doxygen/other')

diff --git a/docs/doxygen/other/logger.dox b/docs/doxygen/other/logger.dox
index 7b0f64e12b..f057e59d9b 100644
--- a/docs/doxygen/other/logger.dox
+++ b/docs/doxygen/other/logger.dox
@@ -205,7 +205,7 @@ input to our logging macros like 'GR_LOG_INFO(LOG, "message")'.
 
 \section logPy Logging from Python
 
-The logging capability has been brought out python via swig. The configuration 
+The logging capability has been brought out python via swig. The configuration
 of the logger can be manipulated via the following calls:
 \code
  from gnuradio import gr
@@ -214,7 +214,7 @@ of the logger can be manipulated via the following calls:
  gr.logger_reset_config()   # Resets logger config by removing all appenders
 \endcode
 
-Once the logger is configured you can manipulate a logger via a wrapper class gr.logger(). 
+Once the logger is configured you can manipulate a logger via a wrapper class gr.logger().
 You can isntantiate this by the following.  (Reference logger.h for list of methods)
 \code
  from gnuradio import gr
diff --git a/docs/doxygen/other/msg_passing.dox b/docs/doxygen/other/msg_passing.dox
index c184681f23..11abf35728 100644
--- a/docs/doxygen/other/msg_passing.dox
+++ b/docs/doxygen/other/msg_passing.dox
@@ -76,7 +76,7 @@ the messages that are posted to it. After using the
 gr::basic_block::message_port_register_in to declare a subscriber port, we
 must then bind this port to the message handler. For this, we use
 Boost's 'bind' function:
- 
+
 \code
   set_msg_handler(pmt::pmt_t port_id,
     boost::bind(&block_class::message_handler_function, this, _1));
@@ -114,7 +114,7 @@ All messages published by the \b src block on port \a pdus will be
 received by \b dbg on port \a print. Note here how we are just using
 strings to define the ports, not PMT symbols. This is a convenience to
 the user to be able to more easily type in the port names (for
-reference, you can create a PMT symbol in Python using the 
+reference, you can create a PMT symbol in Python using the
 pmt::intern function as pmt.intern("string")).
 
 Users can also query blocks for the names of their input and output
diff --git a/docs/doxygen/other/thread_affinity.dox b/docs/doxygen/other/thread_affinity.dox
index bccdd56573..edac813866 100644
--- a/docs/doxygen/other/thread_affinity.dox
+++ b/docs/doxygen/other/thread_affinity.dox
@@ -57,7 +57,7 @@ Where \p mask is a vector of core numbers to set the thread's affinity
 to.
 
 The current core affinity can be retrieved using the member function:
- 
+
 - gr::block::processor_affinity()
 
 When set before the flowgraph is started, the scheduler will set the
-- 
cgit v1.2.3