Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262571AbVC3XjD (ORCPT ); Wed, 30 Mar 2005 18:39:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262553AbVC3XjC (ORCPT ); Wed, 30 Mar 2005 18:39:02 -0500 Received: from eth2613.sa.adsl.internode.on.net ([150.101.239.52]:50653 "EHLO mail.oasissystems.com.au") by vger.kernel.org with ESMTP id S262577AbVC3XiW (ORCPT ); Wed, 30 Mar 2005 18:38:22 -0500 Date: Thu, 31 Mar 2005 09:08:20 +0930 From: John Pearson To: linux-kernel@vger.kernel.org Subject: Re: [PATCH] embarassing typo Message-ID: <20050330233820.GA29221@oasissystems.com.au> References: <200503300053.28553.gene.heskett@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200503300053.28553.gene.heskett@verizon.net> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: -105.8 X-Spam-Report: Spam detection software, running on the system "foghorn2.internal", has examined this email to determine if it is likely to be spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. The presence of these headers does not, by itself, indicate that this is spam; they are provided for your information. The actual score awarded to this email appears in the 'X-Spam-Score' header; if the score is high enough that this is likely to be spam, then the subject line will have been modified or the message rejected, depending on how highly it scored. A summary of the scores awarded by individual tests appears below. If you have any questions, see the administrator of that system for details. Content preview: On Wed, Mar 30, 2005 at 12:53:28AM -0500, Gene Heskett wrote > On Tuesday 29 March 2005 20:40, Dmitry Torokhov wrote: > >On Tuesday 29 March 2005 16:58, Michael Tokarev wrote: > >> Well, it's a matter of readability mostly. ?For now at least, when > >> char is always 8 bytes... > > > >Wow, that's one huge char you have there ;) > > Yeah, I was gonna ask what language is so complex as to need an 8 byte > char? > > Certainly not an earthly one I'd think ;) > [...] Content analysis details: (-105.8 points, 4.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -100 USER_IN_WHITELIST From: address is in the user's white-list -3.3 ALL_TRUSTED Did not pass through any untrusted hosts -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.1 AWL AWL: From: address is in the auto white-list Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1535 Lines: 45 On Wed, Mar 30, 2005 at 12:53:28AM -0500, Gene Heskett wrote > On Tuesday 29 March 2005 20:40, Dmitry Torokhov wrote: > >On Tuesday 29 March 2005 16:58, Michael Tokarev wrote: > >> Well, it's a matter of readability mostly. ?For now at least, when > >> char is always 8 bytes... > > > >Wow, that's one huge char you have there ;) > > Yeah, I was gonna ask what language is so complex as to need an 8 byte > char? > > Certainly not an earthly one I'd think ;) > Might come in handy for Perl 7 Regular Expression syntax... John. -- Voice: +61 8 8202 9040 Email: jpearson@oasissystems.com.au Oasis Systems Pty Ltd 288 Glen Osmond Road Fullarton, South Australia 5063 Ph: + 61 8 82029000 Fax: +61 8 82029001 CAUTION: This email and any attachments may contain information that is confidential and subject to copyright. If you are not the intended recipient, you must not read, use, disseminate, distribute or copy this email or any attachments. If you have received this email in error, please notify the sender immediately by reply email and erase this email and any attachments. DISCLAIMER: OASIS Systems uses virus-scanning technology but accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/