On Jun 12, 2015, at 11:14 PM, Clifford Yapp <cliffy...@gmail.com> wrote:
> On Fri, Jun 12, 2015 at 2:29 PM, Brad Hollister <behol...@soe.ucsc.edu> wrote: >> Hi, >> >> I've created a github repo to push my local revisions -- so that I can >> incrementally develop / track our project requirements. See here: >> >> https://github.com/behollis/brlcad-svn-rev65072-gsoc2015 >> >> I've already implemented some of the CLI commands. Should I create >> patches for each newly implemented command, or wait until there is a >> *significant* amount of new code for a patch? > > My suggestion would be that rather than defining a lot of top level > nmg_* commands, we look at the way the brep command works and go with > subcommands under a top level "nmg" command. Ditto! We are indeed trying to consolidate our command namespace to really as few top-level commands as possible, logically grouping functionality together via subcommands. I suggest creating a patch that only stubs in your single new top-level command with zero or more subcommands, does not need to be complete. Cheers! Sean ------------------------------------------------------------------------------ _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
