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 Subject: RE: setup.exe: Woe is me! From: Robert Collins To: cygwin@cygwin.com In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-knJxPr4WXayFaEUiipEc" Organization: Message-Id: <1051492164.887.49.camel@localhost> Mime-Version: 1.0 Date: 28 Apr 2003 11:09:24 +1000 --=-knJxPr4WXayFaEUiipEc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2003-04-28 at 05:23, Igor Pechtchanski wrote: > I don't know how much extra effort it'll be, but wouldn't a > "log-on-the-spot" command-line option make sense anyway? Or is that what > you meant? Actually, I just meant building setup with the extant patch to change the logging behaviour. A command line option we can include for releases would be neat. The patch Max has just reposted would be a good basis for that.. Rob --=20 GPG key available at: . --=-knJxPr4WXayFaEUiipEc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA+rH9EI5+kQ8LJcoIRAtkMAJ914zUlriizB3MhdZEwdnXcR7oZRQCgjKHF CZpp/c9vrstbVzyY1eOgrOQ= =ZWQD -----END PGP SIGNATURE----- --=-knJxPr4WXayFaEUiipEc--