Massive detabbing of the source

Simon Peyton-Jones simonpj at
Thu Jan 17 15:06:35 CET 2013

Hmm. Precisely because it causes un-forced conflicts, our policy has been: 
	de-tab when you are modifying a file anyway

But if you find files that are stable -- have not been modified for some months -- then yes you could detab them. Perhaps one directory at a time?  

I'm unsure it's worth the bother, but would not want to obstruct.  Others may have views


| -----Original Message-----
| From: ghc-devs-bounces at [mailto:ghc-devs-bounces at]
| On Behalf Of Jan Stolarek
| Sent: 17 January 2013 13:32
| To: ghc-devs at
| Subject: Massive detabbing of the source
| I thought I could clean up the source code from all the tabs and then
| remove {-# OPTIONS -fno-warn-tabs #-} pragmas + comment below it. This
| is a massive change though (140 files would be affected) and I suspect
| it could potentially be a problem to others working on the source (could
| cause some merge problems). So, can I just proceed with cleaning up all
| those 140 files and then send a single patch or should I devide this
| task into smaller ones (e.g. a single patch for every directory in the
| $(TOP)/compiler/) or should I just give up on this idea?
| Janek
| _______________________________________________
| ghc-devs mailing list
| ghc-devs at

More information about the ghc-devs mailing list