Hi Michael, On 2007-09-06 11:37, Michael Beal wrote: > When attempting to send a patch upstream some time ago, someone > suggested I do a diff and send that so everyone could see the change. > I don't much care for doing diffs. Seems a lot cryptic to me. > Personally, I prefer to mark up code with comments about changes. So, > to all the primary devs, I ask: Is there a specific coding style or > coding guidelines I need to use?
Unified diff (generated with diff -Naur against current svn) as a text/plain (or text/x-patch) attachment is pretty much the format we all want. Comments on the patches can be included in the email. Developers get very good at reading through patches in this format. And _unified_ diffs are actually quite readable, I find. (Context diffs not so much.) > I'm thinking about putting together a website for Freevo skins, plugins > and other such generic stuff. I'd like some input on layout and other > considerations. If anyone has any ideas or just plain thinks this is a > bad idea, let me know. John (Molohan) is away for the next few days, but he's our web guy and would be the best one to offer any feedback about this. Cheers, Jason. ------------------------------------------------------------------------- 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/ _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
