On Mon, Mar 10, 2014 at 3:32 AM, Thibaud Guillaume-Gentil <
notifications@github.com> wrote:

> You said:
>
> However, it doesn't seem to be working quite as advertised. Instead of
> delaying when changes exist, it delays always, even if the changes don't
> exist. It's thus acting as an additional latency and slowing down
> responsiveness in all cases.
>
> and I think is it still the case here, no?
>

Not exactly. It always waits X seconds between checks. The old algorithm
would wait X + Y sec between checks if there were no changes, X sec if
there were changes.


-- 
Alex Chaffee - alex@stinky.com
http://alexchaffee.com
http://twitter.com/alexch