From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Stefan Richter <stefanr@s5r6.in-berlin.de>,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] [CodingStyle] Add comment to not put spaces before tabs.
Date: Fri, 25 May 2007 13:29:46 -0700 [thread overview]
Message-ID: <4657473A.6020203@intel.com> (raw)
In-Reply-To: <46573C70.2070209@zytor.com>
H. Peter Anvin wrote:
> Stefan Richter wrote:
>> Auke Kok wrote:
>>> +Don't put spaces before tabs or mix them.
>> Make it "Don't put spaces before tabs."
>>
>> We do mix them if we combine tabs for indentation with spaces for alignment.
>
> It would probably be good to add a pointer to the cleanfile/cleanpatch
> scripts here, too.
ahh yes, I'll incorporate that.
BTW, would it be possible for cleanfile/cleanpatch to dump warnings to stderr
for lines exceeding 80 characters? I think that would really be useful...
Auke
next prev parent reply other threads:[~2007-05-25 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 17:25 [PATCH 1/2] [CodingStyle] Add comment to not put spaces before tabs Auke Kok
2007-05-25 17:25 ` [PATCH 2/2] [condingstyle] Add chapter on tests Auke Kok
2007-05-25 17:34 ` Stefan Richter
2007-05-25 17:40 ` Kok, Auke
2007-05-26 19:27 ` Jan Engelhardt
2007-05-26 20:13 ` [PATCH] " Jan Engelhardt
2007-05-26 22:35 ` Scott Preece
2007-05-27 14:37 ` Stefan Richter
2007-05-27 15:02 ` Jan Engelhardt
2007-05-27 15:23 ` Stefan Richter
2007-05-27 15:52 ` Jan Engelhardt
2007-05-27 21:01 ` Guennadi Liakhovetski
2007-05-27 18:04 ` [PATCH 2/2] " Kok, Auke
2007-05-27 20:17 ` Pekka Enberg
2007-05-27 16:08 ` Jesper Juhl
2007-05-25 17:32 ` [PATCH 1/2] [CodingStyle] Add comment to not put spaces before tabs Stefan Richter
2007-05-25 19:43 ` H. Peter Anvin
2007-05-25 20:29 ` Kok, Auke [this message]
2007-05-25 21:26 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4657473A.6020203@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=stefanr@s5r6.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox