What are you changing?  If you're changing something in an m4 file then you will see a lot of diffs.  If you're adding a new file there will be some diffs but they're not bad.  If you're not doing either one of those things there should be no diffs.

Derek

Sent from my iPad

On Feb 2, 2013, at 3:41 PM, Jed Brown <jedbrown@mcs.anl.gov> wrote:


On Sat, Feb 2, 2013 at 4:34 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kirk-1@nasa.gov> wrote:
> ~/src/libmesh$ git diff --shortstat
>  80 files changed, 19707 insertions(+), 7912 deletions(-)

We aren't *that* pedantic about forcing you to use the same versions.  ./bootstrap will detect older, incompatible versions and then build compatible ones for you.

What's supposed to happen here if I wanted to add a file and send you a pull request? I've got 20kLOC of diff that you surely don't want, but I can't give you a pull request without the generated files because that won't build (until you run ./boostrap, in which case you get an additional diff to the generated file).

I still think the throw-away 'bootstrap' branch is nicer than having the generated stuff in 'master'.
 

What I could do is add a ./bootstrap --compatibility or something that does force exact version matching.