| 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: Tue, 7 Jun 2011 20:54:24 +0300 From: "Amir G." <amir73il@...rs.sourceforge.net> To: Sunil Mushran <sunil.mushran@...cle.com> Cc: Josef Bacik <josef@...hat.com>, linux-ext4@...r.kernel.org, tytso@....edu Subject: Re: [PATCH RFC 00/30] Ext4 snapshots - core patches On Tue, Jun 7, 2011 at 8:14 PM, Sunil Mushran <sunil.mushran@...cle.com> wrote: > On 06/07/2011 09:46 AM, Amir G. wrote: >> >> I understand the bitterness in btrfs community regarding ext4 snapshot >> feature. You might say the same things about ext4 64bit feature. >> I think it is not up to us to decide how it rolls. it's the users >> and companies involved that dictate where the development happens. > > Bitterness is not the issue. The issue is what happens when your > _patron_ has had enough of the project and decides to stop funding. > My patron is not funding the project for the good of humanity it has customers using the product and relying on the snapshot feature. This is what I meant by market forces driving the development decisions. > Are you going to spend your free time maintaining the entire file system? > Nope. But if we accept the premise that the ext4 snapshots feature is something that can drive a business to more income, than I should have no problem finding a new patron if it comes to that. Cheers, Amir. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists