linux-kernel - Re: [PATCH] CodingStyle: multiple updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0802270033310.5714@axis700.grange>
Date:	Wed, 27 Feb 2008 00:40:43 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
cc:	Randy Dunlap <randy.dunlap@...cle.com>, ricknu-0@...dent.ltu.se,
	khc@...waw.pl, bhalevy.lists@...il.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] CodingStyle: multiple updates

On Tue, 26 Feb 2008, Jan Engelhardt wrote:

> +Continuation lines are always shorter than the initial one and are
> +(1) indented as much as the initial line, plus (2) alignment spaces.
> +Spaces are used so as to not cause odd aligning for users wishing to
> +display tabs at sizes other than 8. In the example below, the
> +continuation line of the printk call therefore has two tabs of logical
> +indent, followed by a number of spaces to align it up.

Now, I think, I am not the only one using emacs. Until now the "linux" 
C-style fitted perfectly with the CodingStyle, now it no longer will. 
Namely, emacs puts as many tabs to indent the continuation line as fit 
(i.e., at tab width = 8 spaces it's just (extra indent / 8) tabs plus 
(extra indent % 8) spaces. Is there a way to make emacs behave compatibly 
to this proposal? If not, I would not like to have to re-indent every such 
line manually or have my patches rejected because of this.

Thanks
Guennadi
---
Guennadi Liakhovetski
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/