[PATCH 3 of 4] help: expand the extensions topic

timeless timeless at gmail.com
Sun Jun 21 00:09:44 CDT 2009


> +    Mercurial has a mechanism for adding new features through the
> +    use of extensions. Extensions may bring new commands, or new
> +    hooks, or change some behaviors of Mercurial.

change Mercurial's behavior.

> +    Extensions are not loaded by default for a variety of reasons,
> +    they may be meant for an advanced usage or provide potentially

I generally eschew "usage", if "use" applies, please use it, if
"users" is more relevant, please use that.

> +    dangerous commands (eg. mq or rebase allow to rewrite history),

eg. => e.g.
or => and,
allow => allow users || allow..history => allow history to be rewritten

> +    they might not be yet ready for prime-time, or they may alter

yet ready => ready || yet..time => ready for prime-time yet

> +    some usual behaviors of stock Mercurial. It is thus up to the

note that you've used a slightly different string here than at the
beginning, this doesn't help matters :(

alter some...Mercurial => change Mercurial's behavior.

> +    user to activate the extensions as needed.

the => ''

> +    To enable an extension "foo" which is either shipped with

I'd write: To enable the "foo" extension, either shipped with

> +    You may also specify the full path where an extension resides:

where an extension resides => to an extension

> +    To explicitly disable an extension which is enabled in an hgrc

extension..enabled => extension enabled

> +    of broader scope, prepend its path with !:

i sure hope "of broader scope" is defined somewhere :)



More information about the Mercurial-devel mailing list