On Nov 6, 2007 1:43 PM, Zachary Goldberg <[EMAIL PROTECTED]> wrote: > Who would be responsible for the 'main branch'?
Ok, you already put the "main branch" into quotes, that's important because there is no such thing. But we could agree that someone else would aggregate others changes, test and then publish. Who would step up to do that? I surely can do, since I already read most of the patches to commits list. Maybe someone else with more "house-time" would prefer to do that? Raster? Anyone else? The point is: one could easily create a new branch, import someone's else repository, test and choose if it should keep or not. -- Gustavo Sverzut Barbieri -------------------------------------- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
