hgrc - names of the extensions bundled with Mercurial

[Stanimir Stamenkov]

Tue, 22 Dec 2009 00:59:48 +0100, /Martin Geisler/:

> There is no difference between the two forms.
>
> For each (<name>, <path>) pair, we start by removing 'hgext.' or
> 'hgext/' from the beginning of <name>. If <path> is empty (the "foo ="
> case), we import hgext.<name> and use that as the extension. Otherwise
> we load the file given by <path>.
>
> I've just gone through the extensions and updated the help texts so that
> they all consistently ask you to load them using just the "foo =" form.

I'm referring specifically for the extensions bundled with Mercurial 
[1].  I'm not sure what you've changed but I still see:

hgext.acl=
hgext.hbisect=
hgext.bugzilla =
hgext.churn=
hgext.convert=
hgext.extdiff =
hgext.fetch=
hgext.gpg=
hgext.graphlog =
hgext.hgcia =
hgext.highlight=
hgext.keyword=
hgext.mq =
hgext.notify =
hgext.patchbomb =
hgext.purge=
hgext.record=
hgext.schemes=
hgext.win32mbcs=
hgext.win32text=

and then:

bookmarks =
children =
color =
imerge=
inotify =
interhg =
pager =
parentrevspec =
rebase =
relink =
share =
transplant=
zeroconf=

This one is given two variants:

hgk=/usr/local/lib/hgk.py
hgk=

[1] 
http://mercurial.selenic.com/wiki/UsingExtensions#Extensions_Bundled_with_Mercurial 


-- 
Stanimir