On Mon, Apr 14, 2014 at 3:42 AM, Christopher Sean Morrison <brl...@mac.com> wrote: > I saw it, thanks. A notification is sent out every time a patch is submitted > or changed, so you (and others) don't have to worry or wonder if we notice. > We already know.
Alright. > > Now whether it can or will be reviewed soon is an entirely different matter, > as that depends on timing and dev utility and such. Make sure your patches > apply to unmodified sources and/or have clear instructions that don't make > the reviewer have to jump through hoops. Yes, I have taken care of that by testing the patches many a time on different systems and provided the essential instructions along with them. <snip> > Reformatting code is best done after attaining commits rights. That happens > by having at least a couple "perfect" patches that are useful and require > zero modification by the reviewer. If I am not wrong in getting what you have mentioned, I must stay away from reformatting code as for now. Meanwhile I am getting acquainted with STEPcode and Mediawiki to be able to implement them in my project. -- Thanks Albert www.coderalbert.wordpress.com "If you really look closely, most overnight successes took a long time." ― Steve Jobs ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
