Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <41399CF2.75B039E@dessent.net> Date: Sat, 04 Sep 2004 03:46:10 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: /proc registry access References: <413831C5.6010803@tlinx.org> <41390426.7070100@tlinx.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.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@sources.redhat.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/