Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<41399CF2.75B039E@dessent.net>
Date:	Sat, 04 Sep 2004 03:46:10 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: /proc registry access
References:	<413831C5 DOT 6010803 AT tlinx DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0409030853530 DOT 28876 AT slinky DOT cs DOT nyu DOT edu> <41390426 DOT 7070100 AT tlinx DOT org>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

linda w wrote:

> gotta figure out how to get cvs to work through a proxy and, maybe
> better, set up a cross development environment on linux.  I lost the
> last simple set of instructions I had to build the setup command...sigh.
> 
> I think for the proxy bit, I seem to remember having to use a sockified
> CVS...

Google[1] says that if you have cvs >= 1.12.6 you can specify a http
proxy in the pserver CVSROOT specification:

cvs -d
:pserver;proxy=foo;proxyport=bar:anoncvs AT sources DOT redhat DOT com:/cvs/src co
winsup


However, if you have a SOCKS proxy then you'll indeed need a socksified
version of the cvs client.

Brian

[1] https://www.cvshome.org/cyclic/cvs/dev-http.txt

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -