From: "H. Peter Anvin" <hpa@zytor.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Should "cleanpatch" clean up stretches of space?
Date: Fri, 08 Jun 2007 09:12:00 -0700 [thread overview]
Message-ID: <46697FD0.9070006@zytor.com> (raw)
Hi all,
Right now I have "cleanspace" and "cleanpatch" clean up spaces before
tabs, but it does not compress runs of spaces that aren't followed by a tab.
I could make it do that; I was being conservative when I wrote it and
opted for it not to do so, but I wanted to hear if people think it
should (and if so, what should a reasonable threshold be, in addition
for obviously crossing a tab line? Two spaces? Three? Four? Eight?)
-hpa
next reply other threads:[~2007-06-08 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 16:12 H. Peter Anvin [this message]
2007-06-08 16:25 ` Jan Engelhardt
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=46697FD0.9070006@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®