linux-kernel - Re: [ksummit-attendees] [PATCH] commit: Add -f, --fixes <commit> option to add Fixes: line

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]

Date:	Mon, 28 Oct 2013 23:48:00 +0000
From:	tytso@....edu
To:	Russell King - ARM Linux <rmk+kernel@....linux.org.uk>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Christoph Hellwig <hch@....de>,
	ksummit-2013-discuss@...ts.linuxfoundation.org,
	linux-kernel@...r.kernel.org,
	ksummit-attendees@...ts.linuxfoundation.org
Subject: Re: [ksummit-attendees] [PATCH] commit: Add -f, --fixes <commit>
 option to add Fixes: line

[ I've removed Junio and the git mailing list form the -cc ]

On Mon, Oct 28, 2013 at 11:41:17PM +0000, Russell King - ARM Linux wrote:
> 
> I agree too.  This whole thread seems to be about noise, and I too
> thought there was something about not cross-posting between this list
> and any other list.

We talked about not including patches on a theoretical "git subtree
maintainers list", for noise control purposes, and I think it would be
a good to extend this to the ksummit-* mailing lists as well.

I'm not sure there's an easy way to make mailman reject e-mails that
contain patches, but I'd request that people please honor this
restriction.  If you must, send the patch to the appropriate mailing
list, and then include a lkml.org or some other mail archive link to
the ksummit-* lists.

						- Ted
--
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/