Sweet - that is great news!  Thanks for working this out Ben!


On Mon, Mar 3, 2014 at 9:13 AM, John Peterson <jwpeterson@gmail.com> wrote:

On Mon, Mar 3, 2014 at 8:33 AM, Kirk, Benjamin (JSC-EG311) <benjamin.kirk@nasa.gov> wrote:
Looks like we're in the clear:

> Glad to hear that libHilbert found a home somewhere. Shouldn't be a problem to re-release that under the LGPL.
> It took me a few days to get access to my old university account, but you can find the new source here:
> https://web.cs.dal.ca/~chamilto/hilbert/index.html

I'll work in the update.

Great.  For what it's worth, I checked in the old SVN logs to see what you'd patched in libHilbert over the years, and came up with the following not necessarily exhaustive list:

svn diff -c 2494 > r2494.patch
svn diff -c 2495 > r2495.patch
svn diff -c 2497 > r2497.patch
svn diff -c 3105 > r3105.patch
svn diff -c 3463 > r3463.patch

I tarred these up and attached them to this email...


PS, anyone who wants the final backup of the old libmesh SVN repo can grab it here: https://drive.google.com/file/d/0B9BK7pg8se_iYlFMQ2tzelU2NEk/edit?usp=sharing

You can use the backup just like a normal repo with the file:// URL...

Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
Libmesh-devel mailing list