Am 16.06.2010 13:44, schrieb Antoine Pitrou:
Martin v. Löwis<martin<at> v.loewis.de> writes:
As a maintainer of the PyPI project, it makes your workflow simpler,
- contributors can clone the repo, change the code and ask you for a pull
- you can pull changes by direct hg commands, and merge them
After using Mercurial in one project, I'm skeptical that this really
makes things simpler. I find it very hard to find out what changes a
specific clone has that I still need to integrate. Also, when merging
with conflicts, I find it very difficult to determine whether I merged
all the conflicts correctly (since the diff will show all changes, not
just the conflicts).
So I rather expect things to become more difficult when switching to hg.
I think it would be fair to bring those points on the mercurial mailing-list.
After all we'll be one of their "high-profile" users, so they'd probably like us
to enjoy the experience.
I'm just a hg beginner, so it's probably all my fault, and I'm not using
it correctly.
However, I admit that switching from RCS to CVS was easy, and so was
switching from CVS to SVN. Switching to hg is the most difficult change
for me. I'm probably getting old.
Regards,
Martin
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
