[issue743] enable fetch extension by default

[Charles Samuels]

New submission from Charles Samuels <charles at vmware.com>:

I think the "hg fetch" extension should be enabled by default. Here's some good 
reasons:

- it's passive in that if it's not enabled, and you don't use it, then it makes 
no difference
- it makes training a hell of a lot easier; I can say "just run hg fetch, it's 
like svn up" and leave it at that.
- it's not exactly clear what the difference between "merge" and "update" is 
(to a new user). I can say "run update, merge, commit", but that's really lame 
in a corporate setting where you will be using even a DRCS in a centralized 
manner. It also gives the impression that "mercurial isn't user friendly". If 
they get the "three command incantation" wrong, someone (me) has to merge their 
branches on the "central repository" because "hg push" recommends that they use 
the -f option.
- I also don't want to train people to "add this to the config file because 
this incredibly useful feature is off by default".

Also please realize that I complain about mercurial a lot in bug reports 
because I like it a lot :)

----------
messages: 4010
nosy: charles
priority: wish
status: unread
title: enable fetch extension by default

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue743>
____________________________________________________