sourceforge cvs

[Chuck Mead]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 28 Jan 2003, Net Llama! posted the following:

NL>> I am sitting on a backbone with 622MB of broadband (RH headquarters)
NL>> this is *NOT* a high latency connection... it is SF congestion with
NL>> many, many people using cvs that is causing this problem so no amount of
NL>> compression is going to help. (I have seen this before and recognize the
NL>> behavior)
NL>
NL>I'm not looking for an argument here, just trying to offer a helpful
NL>suggestion.  I've seen the behavior that you're reporting before, and
NL>increasing compression does resolve it.  You're not even willing to try
NL>it?  BTW, i was referring to sf.net as the high latency connection, not
NL>yours, no need to be so defensive.

I am already using compression. Sorry I did not make that clear. 

And yes you are correct it is the sf end of the connection which is high
latency and that is why I would like it if we did not have to suffer
through their problems. At least if something were to happen to it while
we were doing our own cvs we could influence the outcome. As it is we
are slaves to the situation of the moment at sf.

- -- 
Chuck Mead <csm at redhat.com>
Instructor, GLS
RHCE, RHCI, RHCX
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+NqpnNu5VUC9TaJgRAsiIAJ4wocdFTfbHkyFv1BJ/WND+Ostb/gCeN9sq
n3CCR/dMLaZY34H05r6VZnA=
=eS24
-----END PGP SIGNATURE-----