[PATCH] churn: use ui.progress instead of --progress

[Martin Geisler]

Augie Fackler <lists at durin42.com> writes:

> On Thu, Mar 11, 2010 at 8:31 AM, Martin Geisler <mg at lazybytes.net> wrote:
>>
>> I definitely think we should move it into core -- I love it everytime
>> I see a progress bar pop up. I even lovered the delay to 0.5 seconds
>> to get more of them :-)
>
> I'd be +1 on having it in core - I think that progress feedback is one
> place where git out of the box really eats our lunch.
>
>> When it's in the core, I think it should just work right out of the
>> box. People can (probably) disable it by setting delay to a negative
>> value or something like that.
>
> progress.disable = <bool> rather than a magic int, but yeah :)

Ah, great, I knew you had thought of that too! :-) I actually did look
in the module help string for this first. I can understand why this
option isn't mentioned yet since people can still unload the extension.

-- 
Martin Geisler

Fast and powerful revision control: http://mercurial.selenic.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100311/8fa9689b/attachment.pgp>