X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48604FBA.6030003@bmts.com> Date: Mon, 23 Jun 2008 21:36:58 -0400 From: Ralph Hempel User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: setup.exe command line parameters References: <485C0309.7080404@bmts.com> <005601c8d39f$3e3cc550$2708a8c0@CAM.ARTIMI.COM> <485E7502.3030200@x-ray.at> <485EE8C5.8010106@bmts.com> <003701c8d508$cf4aa750$2708a8c0@CAM.ARTIMI.COM> <485F8A81.5020407@bmts.com> <005a01c8d528$fa4197f0$2708a8c0@CAM.ARTIMI.COM> <48603D26.2020302@bmts.com> <20080624004008.GA12901@ednor.casa.cgf.cx> In-Reply-To: <20080624004008.GA12901@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-brucetelecom.com-MailScanner-Information: Please contact Bruce Telecom 519.368.2000 for more information X-brucetelecom.com-MailScanner: Found to be clean X-brucetelecom.com-MailScanner-From: rhempel@bmts.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 Christopher Faylor wrote: > If you are going to be discussing setup development you should subscribe > to the cygwin-apps mailing list. > > I can't speak for the setup.exe developers but I suspect that you should > be just using the CVS head for all of your development. Here's a case of a topic morphing from its original intent in the correct newsgroup to what should really be a new message in a completely different newsgroup. That's what I get for keeping my eyes on the road instead of looking at the map once in a while to see where I'm going :-) I'll move this to the correct group tomorrow... Cheers, Ralph -- 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/