On 2015-02-22, Raf Czlonka <rczlo...@gmail.com> wrote: > On Sun, Feb 22, 2015 at 12:43:57PM GMT, Stuart Henderson wrote: >> On 2015-02-21, Raf Czlonka <rczlo...@gmail.com> wrote: >> > Alternatively, you can use CVSync[0] to get the code. >> >> That is likely going to be worse on a slow/unstable link as you >> are fetching the entire repository history (~2GB rather than ~750MB), >> not just updating the checked-out tree. > > One would think that. However, CVSync + local 'cvs up' is much faster > and more reliable than "remote" 'cvs up'. > > I'm using it daily so this is not speculative - I'm writing from my own > experience. Also, I had very similar issues as the OP. > > Cheers, > > Raf > > P.S. I'm use CVSync with your mirror :^) > >
Interesting.. I stopped running local cvsync to my server at home a while ago, as 'cvs up' from my mirror (over adsl) was faster, not even taking the extra cvsync time into account ;)
