Roy, others,
I checked in a bunch of new features after Roy announced the release the
other day [r5510] to read/write name information from ExodusII meshes.
These new features are all experimental and in-progress right now that I
didn't intentionally want to sneak into the current release. Now that we
are talking about re-releasing a new tarball, I'd be happy to revert those
changes and hold them until after the release cycle since they are not well
vetted at this point. Let me know what you think and I'll take the
appropriate action.
Thanks,
Cody
On Thu, Apr 5, 2012 at 11:10 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> > Hold off on 0.7.3.1 - looks like gzstreams are not getting configured
> > properly on my machine... I'll investigate.
>
>
> Fixed in r5518 - was referencing old shell test variables.
>
> -Ben
>
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Libmesh-devel mailing list
> Libmesh-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
