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

[Martin Geisler]

Daniel Atallah <daniel.atallah at gmail.com> writes:

> 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 :)
>
> Thanks.
>
> I'll include this in the commit message for the most pertinent commit.

Exactly, please it into the main patch.

> 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)?

Yeah, it was. The lines just looked very long to me, but that is because
I'm used to a line length of ~72 characters in a 80 column wide Emacs.
Don't worry about it :)

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/en/services/mercurial/blog/