[Python-Dev] Mercurial migration: help needed
solipsis at pitrou.net
Sat Sep 5 15:26:07 CEST 2009
Le samedi 05 septembre 2009 à 15:19 +0200, "Martin v. Löwis" a écrit :
> No. It's about files that must, when checked out on Windows, have CRLF
> endings, and, when checked out on Unix, have LF endings - i.e. all the
> ..py, .c, .h, and .rst files, plus a couple of others which don't require
> specific treatment.
> IOW, it's about the default behavior, and the majority of new files.
Ok, sorry for the misunderstanding and the lost bandwidth.
> 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?).
More information about the Python-Dev