On Sat, 2008-04-19 at 11:34 -0400, NightStrike wrote: > On 4/19/08, Daniel Berlin <[EMAIL PROTECTED]> wrote: > > The problem with commits is that the average is not what matters. > > Commits are bursty. > > People make 5 commits to different branches in the course of a minute > > or two, then there is nothing for another 15 minutes, etc. > > Oh. Well... I still had fun writing the script :)
Yeah, if performance is an issue, it'd probably help to play with responses to the commit trigger -- maybe wait for 2 minutes for the repo to become idle, and then prevent another update within 5 minutes (picking numbers out of my wossname). -- dwmw2
