From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Jones <davej@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [PATCH -mm] 1/2: MMCONFIG: validate against ACPI motherboard resources
Date: Wed, 30 May 2007 10:40:53 -0700 [thread overview]
Message-ID: <20070530104053.a50c43dd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070530172331.GB2794@redhat.com>
On Wed, 30 May 2007 13:23:31 -0400
Dave Jones <davej@redhat.com> wrote:
> On Wed, May 30, 2007 at 08:05:28AM -0700, Linus Torvalds wrote:
> >
> >
> > On Wed, 30 May 2007, Robert Hancock wrote:
> > >
> > > I'll try and fix up the formatting and repost this patch.
> >
> > Thanks.
> >
> > > I suspect some
> > > of the issues are from the added code clashing with the way the existing
> > > code was formatted.
> >
> > Well, I have to admit that I might not have reacted so much if it hadn't
> > been for the Thunderbird thing, which made it look _really_ strange at
> > first, so then I had to go outside my mail client to look closer. And once
> > I looked closer, I just went "aiieee, it wasn't all the email client" ;)
>
> I got fed up of telling people to reconfigure their MUAs a long time
> ago and ended up with this in my .procmailrc
>
> :0fw
> | /usr/bin/perl -pe 's/^(Content-Type: .*)format=flowed/\1format=flawed/'
>
> It doesn't solve all the worlds problems, but it least makes that crap
> readable in _my_ MUA. Sadly, if it's a patch that I have to apply
> then chances are I'll have to get them to resend it with something
> else anyway, as it's inevitably buggered in some other way because
> thunderbird really is that dire.
>
> I'm convinced there's some contest to see who can make the worst
> graphical mail client for Linux. I'm not sure what the prize is,
> or who's winning, but the entries so far are horrific.
>
Lotus Notes has no serious competition.
Andy's patch-checking script will (should) detect wordwrapping,
tab-expansion and hopefully space-stuffing. When we get that sorted out,
people who submit broken patches to one of the lists should get a robot
reply within minutes telling them what they did wrong, so things will
become largely self-correcting.
I am sooooo looking forward to that thing. <Sends note to Nobel prize
committee>
next prev parent reply other threads:[~2007-05-30 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:03 [PATCH -mm] 1/2: MMCONFIG: validate against ACPI motherboard resources Robert Hancock
2007-05-30 4:45 ` Linus Torvalds
2007-05-30 8:41 ` Matt Keenan
2007-05-30 14:35 ` Robert Hancock
2007-05-30 15:05 ` Linus Torvalds
2007-05-30 15:38 ` Mark Lord
2007-05-30 23:33 ` Robert Hancock
2007-05-30 17:23 ` Dave Jones
2007-05-30 17:37 ` Linus Torvalds
2007-05-30 17:54 ` Dave Jones
2007-05-30 17:40 ` Andrew Morton [this message]
2007-05-31 1:02 ` Robert Hancock
2007-06-04 12:12 ` Olivier Galibert
2007-06-04 14:35 ` Robert Hancock
2007-06-04 15:37 ` Jesse Barnes
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=20070530104053.a50c43dd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=davej@redhat.com \
--cc=hancockr@shaw.ca \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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