Turned all tabs into 4 spaces. Got rid of whitespace at the end of

lines.  Fixed up resulting mis-indented code I noticed (mostly in
files that used 8 space indents, or used 4-space and 8-space indents
in the same file (!)).  Added the emacs tab-var setting for all files,
not just some of them.

I also added in copyright notices for files I noticed that didn't have
them.  We'll want to do another pass-through to fix these up properly,
though.

I used the following perl snippet to check for mis-indented code after
converting tabs to whitespace:

  $ for i in *.{c,h}; do echo $i; perl -nle 'if ($indent > 0) {$sp=" " x $indent; /^$sp[^ ]/ && print "$.: $_"; $indent=0;}; if (/^( *).*{/ ) {$indent=length($1);} else {$indent=0;}' $i; done | less

It had false positives, but hopefully didn't miss anything.

Reviewed by klarlund@google.com


git-svn-id: http://distcc.googlecode.com/svn/trunk@320 01de4be4-8c4a-0410-9132-4925637da917

1 files changed, 9 insertions, 9 deletions

diff --git a/src/mon.h b/src/mon.h
index 8110fed..ad25bb0 100644
--- a/src/mon.h
+++ b/src/mon.h
@@ -1,5 +1,5 @@
 /* -*- c-file-style: "java"; indent-tabs-mode: nil; tab-width: 4 fill-column: 78 -*-
- * 
+ *
  * distcc -- A simple distributed compiler system
  *
  * Copyright (C) 2003, 2004 by Martin Pool <mbp@samba.org>
@@ -14,7 +14,7 @@
  * WITHOUT ANY WARRANTY; without even the implied warranty of
  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
  * General Public License for more details.
- * 
+ *
  * You should have received a copy of the GNU General Public License
  * along with this program; if not, write to the Free Software
  * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
@@ -31,7 +31,7 @@ extern "C" {
 
 
 /*
-    
+
    Writing Monitors for distcc
    ---------------------------
 
@@ -67,9 +67,9 @@ extern "C" {
    distcc does not maintain a history of tasks that have completed.
    Your monitor program must do that if you want to present that
    information.  mon-gnome.c has a simple implementation of this.
-   
 
-   
+
+
    Possible Approaches
    -------------------
 
@@ -141,7 +141,7 @@ extern "C" {
       acquired by calling dcc_mon_poll in order to free the resources
       allocated by the list.
 
-   
+
    So generally, the algorithm you will employ is:
 
     - Acquire a list of jobs by calling dcc_mon_poll.
@@ -150,7 +150,7 @@ extern "C" {
 
     - Free the resources allocated by the list of jobs by calling
       dcc_task_state_free.
-      
+
    For being able to do the second of the three steps listed above, you
    will need to know what information the dcc_task_state struct (which
    represents a job) provides. For a full list of properties, refer to
@@ -194,7 +194,7 @@ extern "C" {
 
 
 
-    
+
 /**
  * Read the list of running processes for this user.
  *
@@ -238,7 +238,7 @@ struct dcc_history* dcc_history_new(void);
  * very desirable thing: the state can change many times per second
  * frequently when several clients are running, and waking up the
  * monitor each time is expensive. */
-    
+
 /**
  * Set up to notify the monitor when the compiler state changes.
  *