Received: by taz.hyperreal.com (8.6.12/8.6.5) id GAA17718; Tue, 2 Jul 1996 06:49:00 -0700 Received: from madhaus.utcs.utoronto.ca by taz.hyperreal.com (8.6.12/8.6.5) with ESMTP id GAA17710; Tue, 2 Jul 1996 06:48:56 -0700 From: rasmus@madhaus.utcs.utoronto.ca Received: from rathaus (rathaus [128.100.102.12]) by madhaus.utcs.utoronto.ca (8.7.4/8.7.1) with SMTP id JAA03355 for ; Tue, 2 Jul 1996 09:48:56 -0400 (EDT) Date: Tue, 2 Jul 1996 09:48:56 -0400 (EDT) Subject: Re: I *don't* want Paul's style guide. To: new-httpd@hyperreal.com In-Reply-To: <9607011519.aa11203@paris.ics.uci.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@hyperreal.com > -1 on using tabs (and yes, I do mean that to be a real veto). In the past > we have lost days of progress due to mismatching patches solely because > of TABs getting lost in the mail (from both users and developers). > CVS helps this for the main source base, but not for code reviews or > for contributions from outside. > > No TABs, even if we have to run expand before every commit. I'd like to veto your veto. The patch argument is a bit silly I think. Simply run "patch -l" and any whitespace differences are ignored. TABS are much too handy to throw away for such a minor issue. The fact that people can set their tab-width to whatever they are comfortable with makes it easier to align the code when you are trying to make sense of it. Personally I always work with a tab-width of 4. -Rasmus