playing nice with cvs/rsync

[Phil Edwards]

On Mon, Jun 14, 2004 at 08:13:55PM -0700, Sean McNeil wrote:
> 
> My question is, what is a good frequency to maintain the cvs repository
> in-sync with the master?  I want to keep relatively current, but I also
> want to play fair with everyone else and not contribute to the
> overloading of the servers.  Any suggestions or unspoken rules on this?

Depends on how frequently you'd normally be updating your sources and
rebuilding, etc, and how comfortable you are with having a broken tree
when somebody's patch goes wrong.

Also, how often do you use CVS commands which access the repository?
If you do a lot of log/annotate/diff work, or flip between branches,
then a local repository is a big win.  Else, it can be an overall loss.

For my GCC work when I'm not committing something, I update my local repo
once a day.  For other projects where I want to stay up to date, but not
bleeding-edge, once a week.


-- 
Behind everything some further thing is found, forever; thus the tree behind
the bird, stone beneath soil, the sun behind Urth.  Behind our efforts, let
there be found our efforts.
              - Ascian saying, as related by Loyal to the Group of Seventeen