| 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
| ||
|
Message-ID: <CACTFLAN_A1k8bA4GWopztCe0sQ6uAE8=iSn2EA2sgaAFi=8-7A@mail.gmail.com> Date: Thu, 7 Mar 2013 13:07:29 +0100 From: Daniel Mack <zonque@...il.com> To: Miles Rout <miles.rout@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Patches Hi Miles, On Thu, Mar 7, 2013 at 11:02 AM, Miles Rout <miles.rout@...il.com> wrote: > I'm probably stepping on some toes here, but is it really necessary to > post raw patches to this list? They do rather clog up one's inbox. It depends what your patches are for. If you're working on a specific subsystem, it might also suffice sending the patches to the appropriate mailing list for that subsystem. Just make sure to always Cc: the maintainers of the bits you're patching, and check the file MAINTAINERS in your Linux tree. Also read up Documentation/SubmittingPatches for general information. > What's wrong with git? Nothing's wrong with git. It's just that sending patches to a mailing list makes it easier for people to comment on them. Daniel -- 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