Sorry I'm late to the party, been in bed with the flu all day. On Dec 12, 2012, at 11:27 AM, Derek Gaston <fried...@gmail.com> wrote: > Also, I have some libMesh changes that I'm going to be making today, so I was > thinking about my Git workflow a little bit. I think even _I_ am going to > clone the libMesh Git repo on GitHub over into my own workspace and work on > my own changes there and then submit a pull request when those changes are > ready. "Submit a pull request" is essentially akin to emailing a patch so > others can ok your work.
I like this idea alot and will probably do the same. Will give me an external place to commit patches and test before pushing to libmesh master. > Now, if I submit a pull request and everyone is ok with it... I can do my own > pull into the officially libMesh git clone on my workstation and merge to > master and push on my own. I just like the idea of ok'ing my patches with a > pull request first. Ditto. I was trying to suggest something like this yesterday, but this is much more clear. Thanks, Paul ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
