[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070605221625.GU31565@havoc.gtf.org>
Date: Tue, 5 Jun 2007 18:16:25 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Russell King <rmk+lkml@....linux.org.uk>
Cc: David Miller <davem@...emloft.net>, alan@...rguk.ukuu.org.uk,
hch@...radead.org, mroos@...ux.ee, linux-kernel@...r.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined
On Tue, Jun 05, 2007 at 11:03:45PM +0100, Russell King wrote:
> On Tue, Jun 05, 2007 at 05:48:30PM -0400, Jeff Garzik wrote:
> > On Tue, Jun 05, 2007 at 10:38:15PM +0100, Russell King wrote:
> > > There is one final point on this which I wish to make, in case anyone
> > > has decided that this is caused by some recent change at my end.
> > >
> > > I've been adding this header to all my messages for about the last seven
> > > years. It's only *just* become a problem because someone here made a
> > > decision that it was a problem.
> >
> > Search LKML for other mentions of Mail-Followup-To; this is far from the
> > first time it's been brought up.
> >
> > I'm probably one of the few who actually investigated why their MUA was
> > suddenly doing weird, RFC-unfriendly things to the To/CC headers,
> > tracking it down the Mail-Followup-To header.
>
> And rather than configuring your MUA to ignore the header...
> You're using mutt, mutt can be configured so.
So, you are seriously proposing that EVERYONE reconfigure their MUA,
because you are sending out bad headers?
Don't you think that is an unscalable solution, and an imposition?
Jeff
-
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/
Powered by blists - more mailing lists