Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933053AbYB0A57 (ORCPT ); Tue, 26 Feb 2008 19:57:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758122AbYB0A5u (ORCPT ); Tue, 26 Feb 2008 19:57:50 -0500 Received: from ug-out-1314.google.com ([66.249.92.170]:20640 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757306AbYB0A5t (ORCPT ); Tue, 26 Feb 2008 19:57:49 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=pBED80XMJsUdeSX0sqi7TAtxAszFBafYGx3m/XLZMhVBBtiCA9y2SmI4O5fucbLrheqhr9H3HIis+K50fuz/xqyZc2A2yDOlomA5XdVutEL7b58G5hh01qxUciod8JWQO3STcr1eqCDnSC0FDxQ9elUtYsRa6kanKLhfVKG1po8= Message-ID: Date: Tue, 26 Feb 2008 16:57:47 -0800 From: "SL Baur" To: "Krzysztof Halasa" Subject: Re: [PATCH] CodingStyle: multiple updates Cc: "Guennadi Liakhovetski" , "Jan Engelhardt" , "Randy Dunlap" , ricknu-0@student.ltu.se, bhalevy.lists@gmail.com, "Linux Kernel Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1204062430.47c488def40a4@portal.student.luth.se> <20080226135444.f83a0536.randy.dunlap@oracle.com> X-Google-Sender-Auth: 46fa802af865e9e0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 556 Lines: 13 On 2/26/08, Krzysztof Halasa wrote: > Hopefully an elisp expert will implement it. Vim people probably need > something like that as well, and the list of editors is a bit longer... The proposed two space change is ugly. Can someone NAK it? -sb (The elisp guy who added the linux c-style) -- 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/