On Tue, 29 Nov 2005 15:48:29 -0600 Brian Mattern <[EMAIL PROTECTED]> babbled:
> On Tuesday 29 November 2005 15:05, Morten Nilsen wrote: > > Brian Mattern wrote: > > > Ok, it looks like we just need to lay out some simple guidelines to make > > > everyone happy. > > > > > > Contributing code is ALWAYS welcome. Write your code, then use 'cvs diff > > > -u' to create a patch. Attach it to an email to this list. If you haven't > > > heard back after a few days, send another response. Or, send a personal > > > email to the first listed AUTHOR for the package. (Sometimes people are > > > busy and don't read the edevel stuff, but most of us feel naked when away > > > from email for more than a day). By this point, if you still haven't > > > heard from the author, most likely some one else will have > > > reviewed/committed your patch. > > > > I never heard anything about the ecore_config patch I sent in.. > > noone even told me it sucked :) > > Oooh slipped by us. :) (Really, I think we need something better than just > the list for tracking patches, but, that's another story...) you're telling me. my current system is to mark any mail with a patch or some important issue and leave it in my inboxes until i finally flush this stuff out. the bigger the patch, the less likely i am to get to flushing. it doesn't scale well - but however u look at it - i cant think of a better way. patches just take a lot of time to read. what i have been doing is trying to DROP working on anything i'm not mother-henning over (right now i mother-hen over eet, embryo, edje, evas, ecore, e17 - i pretty much leave everything else alone). within ecore, i leave ecore_config to andy as he pretty much knows the code the best. the problem is - if you are "looking after" a chunk of code - if you get patches it takes time. the only way to solve it is if multiple people mother-hen over the code, review the patch and then the workload is split. > I'll take a look at it tonight if no one beats me to it. > > On a quick glance, sorting directory first should probably be made an > options. I know I've seen contention on the list over which way is 'correct' > before... > > -- > rephorm > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
