Re: [Libmesh-devel] Thoughts on the next release?

2015-10-30 Thread Kirk, Benjamin (JSC-EG311)
On Oct 29, 2015, at 5:31 PM, John Peterson mailto:jwpeter...@gmail.com>> wrote: The strip_dup_libs.pl fix has been merged, and I also started an 0.9.5 branch with stuff for the next release. For some historical perspective, I also dug some of the older release dates o

Re: [Libmesh-devel] Thoughts on the next release?

2015-10-30 Thread Paul T. Bauman
On Fri, Oct 30, 2015 at 9:46 AM, Kirk, Benjamin (JSC-EG311) < benjamin.k...@nasa.gov> wrote: > > On Oct 29, 2015, at 5:31 PM, John Peterson wrote: > > The strip_dup_libs.pl fix has been merged, and I also started an 0.9.5 > branch with stuff for the next release. > > For some historical perspecti

Re: [Libmesh-devel] Bring pre-github history into the repository

2015-10-30 Thread Roy Stogner
On Fri, 30 Oct 2015, John Peterson wrote: Basically:  .) Make a git svn clone of the old repo, create a branch called pre_git_libmesh .) Merge upstream/master into pre_git_libmesh .) Merge pre_git_libmesh back into master. Wait, so we can do this without a force push? I've wanted to do this

Re: [Libmesh-devel] Bring pre-github history into the repository

2015-10-30 Thread John Peterson
On Fri, Oct 30, 2015 at 11:03 AM, Roy Stogner wrote: > > On Fri, 30 Oct 2015, John Peterson wrote: > > Basically: >> .) Make a git svn clone of the old repo, create a branch called >> pre_git_libmesh >> .) Merge upstream/master into pre_git_libmesh >> .) Merge pre_git_libmesh back into master. >>

[Libmesh-devel] Bring pre-github history into the repository

2015-10-30 Thread John Peterson
Basically: .) Make a git svn clone of the old repo, create a branch called pre_git_libmesh .) Merge upstream/master into pre_git_libmesh .) Merge pre_git_libmesh back into master. The merges are trivial (no conflicts) because the git svn clone puts everything in the old SVN {branches,tags,trunk}