lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070605145603.GF31565@havoc.gtf.org>
Date:	Tue, 5 Jun 2007 10:56:03 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Russell King <rmk+lkml@....linux.org.uk>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Christoph Hellwig <hch@...radead.org>,
	David Miller <davem@...emloft.net>, mroos@...ux.ee,
	linux-kernel@...r.kernel.org
Subject: Re: libata & no PCI: dma_[un]map_single undefined

On Tue, Jun 05, 2007 at 03:51:49PM +0100, Russell King wrote:
> On Tue, Jun 05, 2007 at 10:35:23AM -0400, Jeff Garzik wrote:
> > 
> > BTW, please fix your mailer.  It emits Mail-Followup-To headers that
> > hijack everyone on the thread into the To field, breaking the normal
> > LKML To/CC standard replying mechanism that has been working for a
> > decade.
> 
> Sorry, I will not.  My local policy (which I have the utmost right to
> have) is that I do not wish to be CC'd on responses to replies to my
> posts.  Additional useless CC's are a waste of my limited bandwidth
> and resources.
> 
> It's a question of local policy required by local resource limitations.
> 
> So I give you a choice: you can either have the benefit of me reply and
> put up with the follow up header, or I will arrange to never reply to
> your messages ever again (which may involve me never reading one again).
> Which would you prefer?

Your personal preference is fine with me.

Just stop hijacking -everyone else's- preferences along with it.

A far more community-friendly method that operates within existing email
standards is to filter out duplicate message ids on your side.

	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

Powered by Openwall GNU/*/Linux Powered by OpenVZ