| 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: <20090804221200.GP28678@mit.edu> Date: Tue, 4 Aug 2009 18:12:00 -0400 From: Theodore Tso <tytso@....edu> To: Valerie Aurora <vaurora@...hat.com> Cc: linux-ext4@...r.kernel.org, Eric Sandeen <sandeen@...hat.com>, Ric Wheeler <rwheeler@...hat.com> Subject: Re: Fix device too big bug in mainline? On Tue, Aug 04, 2009 at 05:29:37PM -0400, Valerie Aurora wrote: > > Yeah, it's pretty hard to keep track of which branch does what after > several months go by. Maybe next time we can sync up first if it's > been a while since the last review/pull request. > Well, if you are planning on doing more e2fsprogs work, why not work against a shared patch queue which is under git control? That way we don't need to do explicit sync ups. Once we have more than one person with write access into the patch queue, if someone plans to make changes that involve reorganizing or refactoring patches, they should send e-mail to take a "lock" on the patch queue. I normally work on the patch queue in concentrated bursts, usually in the evenings or on the weekends, so if you're going to "take the lock" to work on the patch queue during the day, we're not likely to collide with each other. I believe this will be a far more efficient way of working together, which won't require massive "sync up" efforts. - Ted -- 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