On 05/09/2014 06:58 PM, Derek Gaston wrote: > I think I've had too much coffee this afternoon... let's try that last > email again... this time in English: > > > > Sorry for one more email on this topic... but if you want to see how > we track libMesh revisions look at our repo: > https://github.com/idaholab/moose > > See that libMesh directory? Notice how it has a Git hash right next > to it? We're using Git Submodules... and that hash is the current > version of libMesh that we're using (ie that our customers are > receiving) automatically just by cloning our repo and running "git > submodule init; git submodule update" (they actually run a small > script in our repo that does that for them). > > In this way - all we need to do is update the hash of the version of > libMesh we're using and all of our customers get the new revision of > libMesh automatically when they update their version of our software > (and after running "git submodule update"... again through a script). > > Nice and tidy - and no waiting on libMesh releases. > > > Okay, I understand the issue. Currently I have a workaround with forward declaratiosn in my code, so I can wait some time for the next release. May be meanwhile I learn how to use git.
Michael. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
