| 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: Thu, 1 Feb 2007 12:43:56 +0100 (MET) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: Lee Revell <rlrevell@...-job.com> cc: Theodore Tso <tytso@....edu>, Greg KH <greg@...ah.com>, Nicolas Mailhot <nicolas.mailhot@...oste.net>, linux-kernel@...r.kernel.org Subject: Re: Free Linux Driver Development! On Jan 31 2007 18:59, Lee Revell wrote: > On 1/31/07, Theodore Tso <tytso@....edu> wrote: >> >> More specifically, Dave said that it "seemed rude" to just take the >> driver and send updates, but maybe the best way of dealing with >> out-of-tree drivers like lirc is to treat the out-of-tree drivers as a >> kind of spec release, and just have someone in the community forcibly >> take the code, fix it up, and then get it merged. > > But if the maintainer is unwilling to work with the kernel developers, > the driver won't get bugfixes or updates for new hardware. Talk about util-linux and rpm, whose maintainers were/are unwilling to give back the project to those who would really like to work on it. At least I don't differentiate between userspace and kernelspace when it comes to "hijacking projects back for the better". foobar is left where it is, and is commonly forked into foobar-ng. It's just naming. Just pull in lirc and tag it lirc-ng. Jan -- ft: http://freshmeat.net/p/chaostables/ - 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