Remove trailing whitespace.

Change-Id: I1e0948da34bac278edc62cd63dedd08112426e7a
Signed-Off-By: Jelmer Vernooij <jelmer@samba.org>
Reviewed-by: David Disseldorp <ddiss@samba.org>

1 files changed, 13 insertions, 13 deletions

diff --git a/pidl/README b/pidl/README
index c6b7e117926..7c8ecd1f8ba 100644
--- a/pidl/README
+++ b/pidl/README
@@ -1,25 +1,25 @@
 Introduction:
 =============
-This directory contains the source code of the pidl (Perl IDL) 
-compiler for Samba 4. 
+This directory contains the source code of the pidl (Perl IDL)
+compiler for Samba 4.
 
 The main sources for pidl are available using Git as part of
 the combined Samba 3 / Samba 4 tree. Use:
 git clone git://git.samba.org/samba.git
 
-Pidl works by building a parse tree from a .pidl file (a simple 
-dump of it's internal parse tree) or a .idl file 
-(a file format mostly like the IDL file format midl uses). 
-The IDL file parser is in idl.yp (a yacc file converted to 
+Pidl works by building a parse tree from a .pidl file (a simple
+dump of it's internal parse tree) or a .idl file
+(a file format mostly like the IDL file format midl uses).
+The IDL file parser is in idl.yp (a yacc file converted to
 perl code by yapp)
 
-After a parse tree is present, pidl will call one of it's backends 
-(which one depends on the options given on the command-line). Here is 
+After a parse tree is present, pidl will call one of it's backends
+(which one depends on the options given on the command-line). Here is
 a list of current backends:
 
 Standalone installation:
 ========================
-Run Makefile.PL to generate the Makefile. 
+Run Makefile.PL to generate the Makefile.
 
 Then run "make install" (as root) to install.
 
@@ -55,9 +55,9 @@ Parse::Pidl::Util - Misc utility functions used by *.pm and pidl.pl
 Parse::Pidl::Typelist - Utility functions for keeping track of known types and their representation in C
 
 Tips for hacking on pidl:
- - Look at the pidl's parse tree by using the --keep option and looking 
-   at the generated .pidl file. 
- - The various backends have a lot in common, if you don't understand how one 
+ - Look at the pidl's parse tree by using the --keep option and looking
+   at the generated .pidl file.
+ - The various backends have a lot in common, if you don't understand how one
    implements something, look at the others
  - See pidl(1) and the documentation on midl
- - See 'info bison' and yapp(1) for information on the file format of idl.yp 
+ - See 'info bison' and yapp(1) for information on the file format of idl.yp