Fwd: Switch to git?

[BOGGESS Rod CORE]

Please note that the Tenova Group has adopted a new e-mail domain (@tenova.com).
I kindly ask you to update your contact records accordingly.


Tenova: advanced technologies for the metals and mining industries
Visit our website at www.tenova.com
------------------------------------------------------------------
Confidentiality Notice : This message, together with its attachments, contains strictly confidential information and is intended only for the addressee identified above,who is the sole party authorized to use
 and copy it and, assuming any related liability , to forward it to others. Anyone receiving this message by mistake or reading it without authorization is hereby notified that storage, reproduction, disclosure or distribution of the message to persons other than the addressee is strictly forbidden. They are asked to return the message immediately to the sender and to erase the original message received.
Thank you.



-----Original Message-----
From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com] On Behalf Of Angel Ezquerra
Sent: Monday, November 18, 2013 3:27 AM
To: Lester Caine; Martin Geisler
Cc: anatoly techtonik; mercurial
Subject: Re: Fwd: Switch to git?

Basically he said that it was not clear to him (and I assume that to many other people) that the core extensions that ship with mercurial are as well maintained as the rest of mercurial's commands. He said that he was scared to enable them because in the git world even first party extensions are somewhat flaky and because he did not know if these extensions could change the behavior of core hg commands in subtle ways.

:-:-:-:-:-:-:-:-:

So, if we could query the user at installation on which extensions should be enabled, or perhaps on first use, would this make these extensions seem less experimental and more like a natural extension, or options, of the core repository?