Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <010801c1a462$a1921420$81293c3e@Obsession> Reply-To: From: "keith_starsmeare AT yahoo DOT co DOT uk" To: References: <00b301c1a45e$82614b60$81293c3e AT Obsession> <3C4F3D42 DOT 2080804 AT ece DOT gatech DOT edu> Subject: Re: setup.exe command line options Date: Wed, 23 Jan 2002 23:06:14 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 ----- Original Message ----- From: "Charles Wilson" To: Cc: Sent: Wednesday, January 23, 2002 10:46 PM Subject: Re: setup.exe command line options > Release early and often. Go ahead and publish what you have, against > current CVS. You only need to #ifdef stuff out if it will actually > BREAK something that is currently working. If it's, say, the handler > for an incompletely implemented commandline option, then it won't break > anything (unless someone actually tries to USE that commandline option.) > - in that case, it doesn't need to be #ifdef'ed. That's good advice. Thanks! I'll get it bundled up and fired off to cygwin-patches first thing in the morning. Keith