| 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
| ||
|
Date: Wed, 24 Jan 2007 16:13:48 +0100 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Kristian Høgsberg <krh@...planet.net> CC: linux-kernel@...r.kernel.org, linux1394-devel@...ts.sourceforge.net Subject: Re: In-tree version of new FireWire drivers available Kristian Høgsberg wrote: > Hosting this on freedesktop.org should be fine, > though kernel.org may be more appropriate :) At the moment, a host outside of kernel.org is actually better for gitweb lurkers. (But I trust that kernel.org will get up to speed again soon.) > Stefan, I'm still not sure what the work flow should be > here, do you want to just pull these changes or should I send the 13 > patches to linux1394-devel? IMO: Posting patches to linux1394-devel is a must for anything that is meant to go to -mm or ultimately to mainline. In some cases, patches should also be Cc'd to linux-kernel or specialized lists like linux-scsi or linuxppc-dev etc. depending on the issue. I think linux1394-devel can bear the additional traffic from this new development. The question is whether you will post what you wrote, or if I will post what I pulled from you... -- Stefan Richter -=====-=-=== ---= ==--- http://arcgraph.de/sr/ - 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