Antoine Pitrou <solipsis at pitrou.net> 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. -- Martin Geisler VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20090905/ade522ec/attachment-0001.pgp>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4