On Tue, Jan 24, 2012 at 9:39 AM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > On Tue, 24 Jan 2012, John Peterson wrote: > >> On Tue, Jan 24, 2012 at 9:01 AM, Kirk, Benjamin (JSC-EG311) >> <benjamin.kir...@nasa.gov> wrote: >>> >>> I've got no issues with this. >> >> >> OK cool. >> >> I'll work on this in the next couple of days or so... > > > I forgot to respond, didn't I?
I took your silence as tacit approval ;0) > I see no point in having SVN tags in each file; go right ahead and > remove them. There is one useful feature I've seen a coworker use > along those lines, though: configure can be used to put a version > string into the final product automatically, querying SVN to get a > revision number as well as whether or not the "svn diff" is clean. It > would occasionally be nice to be able to see, at the top of executable > output, precisely which libMesh version produced it. Yeah, I do think that would be really useful. By "final product" do you mean a string in the executable, a line in xda/exodus output, both? Maybe your coworker could send you his m4 script for doing this? > On the other hand, I didn't think this feature was useful enough to > put into libMesh right away, and I doubt I'll be getting around to it > soon... Shouldn't be too bad to at least get the configure stuff up and running, even if the version string doesn't make it into the rest of the library right away. -- John ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
