Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Robert Collins" To: "'Kilroy, David'" , Subject: RE: Re[3]: cygwin download incomplete - try again - loop? Date: Sat, 8 Jun 2002 01:11:27 +1000 Message-ID: <009b01c20e35$990ce590$0200a8c0@lifelesswks> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-reply-to: <0DB4E7930F5CD411AC93009027EE744C0DE7659F@ddcexch.ddcnet.detroitdiesel.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > -----Original Message----- > From: cygwin-owner AT cygwin DOT com > [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Kilroy, David > In my opinion, the rfc1738 code should be fixed so it doesn't > choke on null > or empty strings (which I think is reasonable), and then you > don't need > special code to identify your local cache. Yes but.... The rfc1738 code is ok, it's the C++ classes that are choking, and fixing them is a little harder. Adding overhead to rfc1738 is not good either though :[. > Hope that helps. It does, thanks. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/