[cvsnt] Force commit

Michael Wojcik Michael.Wojcik at microfocus.com
Wed Dec 13 18:34:46 GMT 2006

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Glen Starrett
> Sent: Wednesday, 13 December, 2006 12:15
> To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
> Subject: Re: [cvsnt] Force commit
> Gerhard Fiedler wrote:
> > Try working with a server where the connection is not so good: slow
> > high latency.
> The other side of the coin is that bandwidth is (relatively) 
> cheap now. 

Bandwidth does nothing to address actual channel latency, which is often
far more of an impediment to using CVS remotely.

I work in the US, and my primary CVS server is in the UK.  Bandwidth is
not a problem, except occasionally for very large checkouts (eg when
pulling an entire new module that contains lots of large binary files) -
and then there's always something else I can do while I'm waiting.

Latency, on the other hand, makes actions such as diffing a lot of files
take much longer - and in my experience those are much more common than
bandwidth-bound actions, and also more likely to affect whatever I want
to do in the foreground.

It's not enough of an issue for me to warrant remediation, but it could
well be for others.

Michael Wojcik
Principal Software Systems Developer, Micro Focus

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook