> On Apr 13, 2014, at 11:31 AM, albert coder <eralbert9...@gmail.com> wrote: > > Hello Sean, like you had suggested, I have submitted two patches in > the patch format to the patches tracker. Here is the link to the > second patch that I have submitted...[snip]
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. 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. > I am looking forward to revise the whole code according to the > standards and submit this effort as my third patch. 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. Cheers! Sean ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
