Antoine Pitrou firstname.lastname@example.org writes:
Le samedi 05 septembre 2009 à 15:19 +0200, "Martin v. Löwis" a écrit :
In addition, a DVCS brings in another problem dimension: when people push their changes, they have *already* committed them - and perhaps not even they, but a contributor from which they had been pulling changes. The bogus change may have been weeks ago, so the subversion solution (of rejecting the commit to happen) doesn't quite work that well for a DVCS.
I don't think this problem is really serious. If the push fails, you can just commit (locally) a new changeset that repairs the EOL or indentation problems, and push the whole bunch of changesets again (I assume the server-side hook will not examine changesets individually, but only the last of them?).
Yes, the server-side hook will have to work like this in order for people to fix mistakes like you just described.