Jason Tackaberry wrote: > 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.)
Right. Doc inside the source is also very helpfull. Besides that, I wrote down some coding style rules. Not every rule is as important as the other one and not every dev uses these rules, but it is a good guideline: http://freevo.sourceforge.net/cgi-bin/doc/CodingStandard Dischi -- Theorem: a cat has nine tails. Proof: No cat has eight tails. A cat has one tail more than no cat. Therefore, a cat has nine tails.
pgpxHEGZkQ51O.pgp
Description: PGP signature
------------------------------------------------------------------------- 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 Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
