-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Georg Brandl wrote:
Am 02.07.2010 15:48, schrieb anatoly techtonik:
On Fri, Jul 2, 2010 at 11:33 AM, Georg Brandl <g.brandl@gmx.net> wrote:
So, if I understand correctly - there are no Mercurial mirrors for testing at the moment, There are repositories at http://hg.python.org/; the "cpython" one represents the result of conversion at some point in time. What is the problem with realtime synchronization and working with already up to date Mercurial mirror of central SVN repository?
The specifics of the conversion process are not nailed down yet. Therefore, the exact translation of SVN to Hg commits will change, and with it the Mercurial revision IDs, for example.
Development will continue in SVN repository until everybody is ready for final migration in X weeks later. Is that right? No; as soon as we switch, SVN will be read-only. Why don't allow people who already know Mercurial use Mercurial and those who prefer Subversion use that. If Mercurial allows to submit to Subversion - why people can't use that while we writing tutorials and answering question about workflow?
I don't think that we have enough manpower to maintain such a bridge indefinitely.
The code.python.org/hg mirror has been running for many months now: As a non-committer, I have been able to use its 2.6 branch and the trunk with hg to test / develop / submit patches. Can somebody comment on how much ongoing effort is required to keep that mirror running? I know that the hg / git / bzr mirrors I set up for the repoze SVN repository haven't require any ongoing effort, after the initial day or two of setup effort. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwuARwACgkQ+gerLs4ltQ6rUgCfU2NSdjz+pIY1I95OnpRMU5Fx 22gAn1Zu+KGOaNgYJYJ7c9NKzr3ICxS+ =wIB0 -----END PGP SIGNATURE-----