Mercurial > hg
view tests/test-install.t @ 13760:ed97955e0c04
convert/mtn: add support for using monotone's "automate stdio" when available
Currently the convert extension spawns a new mtn process for each
operation. For a large repository, this ends up being hundreds of
thousands of processes. The following enables usage of monotone's
"automate stdio" functionality - documented at:
http://www.monotone.ca/docs/Automation.html#index-mtn-automate-stdio-188
The effect is that (after determining that a new enough mtn executable
is available) a single long-running mtn process is used for all the
operations, using stdin/stdout to send commands and read output.
This has a pretty significant effect on the performance of some parts
of the conversion process.
| author | Daniel Atallah <daniel.atallah@gmail.com> |
|---|---|
| date | Wed, 23 Mar 2011 14:26:56 -0400 |
| parents | 85d74f6babf6 |
| children | 797bf1dc1ff8 |
line wrap: on
line source
hg debuginstall $ hg debuginstall Checking encoding (ascii)... Checking installed modules (*/mercurial)... (glob) Checking templates... Checking commit editor... Checking username... No problems detected hg debuginstall with no username $ HGUSER= hg debuginstall Checking encoding (ascii)... Checking installed modules (*/mercurial)... (glob) Checking templates... Checking commit editor... Checking username... no username supplied (see "hg help config") (specify a username in your configuration file) 1 problems detected, please check your install! [1]