From: Dave Jones <davej@redhat.com>
To: "Langsdorf, Mark" <mark.langsdorf@amd.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [PATCH] Hardware P-state driver for AMD Opterons, etc.
Date: Mon, 5 Jun 2006 12:40:39 -0400 [thread overview]
Message-ID: <20060605164039.GA15579@redhat.com> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84305350551@SAUSEXMB1.amd.com>
On Mon, Jun 05, 2006 at 10:18:10AM -0500, Langsdorf, Mark wrote:
> > Mark, your editor seems to use a mix of spaces and tabs,
> > which looks really strange. I've fixed up the few cases that
> > stood out, so you may want to base your next diff on what
> > turns up in -mm4 when Andrew releases that tree.
>
> I'll do that.
Great, thanks.
> Sorry for the whitespace confusion; I thought I was running
> pure vim and it was doing the right thing.
I have this in my .vimrc ...
"flag problematic whitespace (trailing and spaces before tabs)
"Note you get the same by doing let c_space_errors=1 but
"this rule really applys to everything.
highlight RedundantSpaces term=standout ctermbg=red guibg=red
match RedundantSpaces /\s\+$\| \+\ze\t/
"use :set list! to toggle visible whitespace on/off
set listchars=tab:>-,trail:.,extends:>
Which is really handy when reviewing diffs.
I usually also do a search for tabs too, and due to "set hls",
any mix of spaces/tabs usually stands out, and if it's on a +/-
line of a diff, I usually just fix the diff 'in-place' rather
than fixing the file & rediffing.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-06-05 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 15:18 [PATCH] Hardware P-state driver for AMD Opterons, etc Langsdorf, Mark
2006-06-05 16:40 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-02 22:45 Langsdorf, Mark
2006-06-04 17:18 ` Dominik Brodowski
2006-06-04 23:36 ` Dave Jones
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=20060605164039.GA15579@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=mark.langsdorf@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.