Heh heh, yes, as a former national lab employee I am well acquainted with the well-polished cogs of bureaucracy.
Daniel, I'll go ahead and put together a test case and figure out how to push the changes to you on Git - thanks for the suggestion. Charles On Thu, Mar 20, 2014 at 8:24 AM, Guyer, Jonathan E. Dr. < [email protected]> wrote: > > > > On Mar 20, 2014, at 11:16 AM, "Daniel Wheeler" < > [email protected]> wrote: > > > > Also, would you like to patch FiPy yourself and add in the test case? > > That way you will get recognition and have your name on the list of > > contributors. You could just push your changes to a public repository > > (Github for example) and then I can pull from there. > > It is also possible to have git generate a patch that will preserve your > authorship. > > > > BTW We will be switching to Github soon, which will make this process > > much easier. > > We *intend* to switch to Github soon. It has not been authorized. The > mills of Government grind slowly, yet they grind exceedingly small. > > > _______________________________________________ > fipy mailing list > [email protected] > http://www.ctcms.nist.gov/fipy > [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ] >
_______________________________________________ fipy mailing list [email protected] http://www.ctcms.nist.gov/fipy [ NIST internal ONLY: https://email.nist.gov/mailman/listinfo/fipy ]
