Integrating extensions into core?

Dirkjan Ochtman dirkjan at
Mon Aug 10 06:27:15 CDT 2009

On Mon, Aug 10, 2009 at 13:09, Dan Villiom Podlaski
Christiansen<danchr at> wrote:
> True, but it's a simple and useful command. If nothing else, it could be
> integrated as ‘commit --interactive’. Isn't that how Git does it?

We should start by adding the --interactive option when record is enabled.

> Another alternative would be to retain status quo by getting rid of another
> command. For example, the ‘locate’ and ‘manifest’ commands are very close to
> each other in semantics, and perhaps they could be merged into one?

Making manifest an alias for locate sounds good to me (that would need
porting the -v/--debug bits, to locate, though). hg tip seems rather
superfluous, as well (and would be replaced by hg log -rtip which I
would expect comes more naturally to people, anyway).

> For what it's worth, I'd consider ‘purge’ another candidate for integration.
> Granted, adding any of these commands to the default install would clutter
> the help output a bit. On the other hand, the current help is quite
> cluttered; do you mean that cleanups and reorganisations should come before
> adding any more commands?

I wouldn't mind integrating purge, but I don't really use it that
often, either. I don't think there should be hard and fast rule that
we have to remove one command for each we add (I think we'd run into
backwards compatibility concerns anyway), but I'd rather be
conservative in adding stuff.



More information about the Mercurial-devel mailing list