casting a negative number to an unsigned int caused badness here, it seems the - 18 magic number can cause some issues depending on parsed_libmesh_configure_info[0].size().  Since std::setw() seems to want an int, cast instead to an int and let it handle the negative as before.
avoid std::cout << unsigned char problem
eigen 3.2.1->3.2.2
Merge pull request #336 from libMesh/eigen_3.2.2_refresh

eigen 3.2.1->3.2.2
rbOOmit change. Added RBEvaluation::read_in_vectors_from_multiple_files, which
allows us to read in vectors from multiple files without renumbering the mesh
dofs on each read.
Enforce prior to refinement for node mismatch

Enforce mismatch prior to refinement at edge level
Adding Rabiti, 2014
Update traffic
Bugfix: make old_dof_indices ordering consistent

We moved the SCALAR dofs to their variable number position in
dof_indices, but didn't make the same update to old_dof_indices
Fix cut-and-paste atavism

Apparently vim's d and p commands are not artificially intelligent.
I should file a feature request.
Merge pull request #340 from libMesh/old_SCALAR_indices

Bugfix: make old_dof_indices ordering consistent
Fix some cast_int calls.

We can't call cast_int<unsigned> on something intentionally
larger than max(unsigned).
The coupled_system.in options were redundant

And worse, they were overwriting the general.in options
Fix spacing, formatting issues.

Remove unnecessary const_cast.
Factor out common code into helper function.
Adding gdb_backtrace() function.
GCC warned about ignoring the return code for the system call, so
let's not ignore it.
Reorganize helper functions into anonymous namespace.

Even if your compiler doesn't support the C++ ABI demangling stuff or
GLIBC backtrace(), we can try to get a gdb backtrace.
Merge pull request #339 from libMesh/enforce_mismatch_prior_to_refinement

Enforce prior to refinement for node mismatch
Update traffic.