-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/02/11 11:19, M.-A. Lemburg wrote: > I don't understand why the developers have to follow the tools and > not the tools the developers.
Well, the tool is designed for a particular workflow. If you do something else, you are fighting the tool and not taking advantage of its bigger strenght. I am advocating a particular workflow (reverse to current) because it is "natural" to mercurial and I find it sensible. That said, the fact is that current workflow can not be used comfy with current mercurial. That is a shameful limitation, I do agree. Some people is working in solving this limitations. But we have to consider if using a "non natural" workflow would alienate new coders familiar with "natural" mercurial workflow. Since one of the objectives of HG migration is to ease external contributions, doing thing "the right way" would help too. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:j...@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/ iQCVAwUBTUvm/plgi5GaxT1NAQJwegP/f5N5PzUpwchEoh1ZeJGccuoGSVj7crTx 96hDNaQEcd9GG7V8IQ2+LXkjwF/HkCshkuyO2XMPFBVahzKOidlG5zEv4bAzDdvY lpiqo70sJYJt7doTwTxQx4v9lbuqYD0gHiv+3Sw06887gqyR05YqCdhcm8NgoNFg +YfLwmrwvu8= =iIIh -----END PGP SIGNATURE----- _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
