All ssh repos can now be accessed by using ssh://hg@hg.python.org/repo instead of ssh://hg@hg.python.org/repos/repo. While the old way should continue to work, the new address should be considered preferable.
Cheers,
Dirkjan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/11/10 14:48, Dirkjan Ochtman wrote:
All ssh repos can now be accessed by using ssh://hg@hg.python.org/repo instead of ssh://hg@hg.python.org/repos/repo. While the old way should continue to work, the new address should be considered preferable.
Are those repositories read/write?. What is their use TODAY?. Only for being ready for 12 december?.
The push will be thru SSH only?. No option for HTTPS pushing?.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQCVAwUBTO0m35lgi5GaxT1NAQK9ugP9EcqWszLqtRsodWjJF8i6Pvk/Ni+g3H4H JuAIqx6gnOMnzGpNOE1nM/aI09t+Yqeqhqrep+vnkTLGxns+/9ASRUWEEqdLUFJr gJ9Y3G6vPOTsxOcUefXAKeK/efZPrMwnKUH/lvTRZli9L/bZ9AgAabhyM6Vkj9CK Klth5NjfH1Q= =nqnC -----END PGP SIGNATURE-----
Am 24.11.2010 15:53, schrieb Jesus Cea:
On 24/11/10 14:48, Dirkjan Ochtman wrote:
All ssh repos can now be accessed by using ssh://hg@hg.python.org/repo instead of ssh://hg@hg.python.org/repos/repo. While the old way should continue to work, the new address should be considered preferable.
Are those repositories read/write?. What is their use TODAY?. Only for being ready for 12 december?.
Some of the repos are already used productively, such as distutils2 and the benchmarks repo, some are used by those helping with the migration, such as hooks and pymigr. The cpython one will become the test repo once Dirkjan is done with his schedule.
The push will be thru SSH only?. No option for HTTPS pushing?.
No; that would be just another infrastructure for us to handle, plus we would need to maintain passwords for every user. Since the current SVN also only allows commit via ssh/public-key, I don't see a problem doing the same for hg.
Georg
On 11/24/10 8:48 AM, Dirkjan Ochtman wrote:
All ssh repos can now be accessed by using ssh://hg@hg.python.org/repo instead of ssh://hg@hg.python.org/repos/repo. While the old way should continue to work, the new address should be considered preferable.
I'd suggest deleting the /repos/ URIs eventually (as in before the end of the year). I don't see the need to keep them around and have the maintenance burden.
Thanks everyone for working on the hg migration. I can't wait.
-- Eric.
On Wed, Nov 24, 2010 at 15:57, Eric Smith eric@trueblade.com wrote:
I'd suggest deleting the /repos/ URIs eventually (as in before the end of the year). I don't see the need to keep them around and have the maintenance burden.
Maybe, but it's currently like three lines in a script, not as if there's a huge maintenance burden.
Cheers,
Dirkjan
participants (4)
-
Dirkjan Ochtman -
Eric Smith -
Georg Brandl -
Jesus Cea