[PATCH 0 of 3 V2] Add support for using monotone's "automate stdio" to the convert extension

Daniel Atallah daniel.atallah at gmail.com
Thu Mar 24 16:23:07 CDT 2011

On Thu, Mar 24, 2011 at 14:18, Martin Geisler <mg at aragost.com> wrote:
> daniel.atallah at gmail.com writes:
>> (Updated set of patches based on review of the first version)
>> Add support for using monotone's "automate stdio" to the convert
>> extension
>> 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.
> I think the above text is so good that it should be put into the commit
> message after being wrapped like I did above :)


I'll include this in the commit message for the most pertinent commit.

I'm a little confused what you mean about the wrapping though - do you
mean at under 80 characters (because I thought my email was already
wrapped at that level)?


More information about the Mercurial-devel mailing list