Comment 5 for bug 213032

Hi,

so if for example a commit message, email-address gets changed:

someone who pulls / merges from the changed repo won't simply retrieve the diff, but he will also retrieve the changed metadata. (in any revision back the whole history)
This wouldn't produce much overhead, since commit messages and e-mail-addresses are usually short. Of course one could deactivate/activate this behaviour with a command-line switch.

I really don't understand why this would complicate the model? There's a change in metadata, which gets transported the moment, where an update / pull / merge happens.

Cheers