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: <000e01c1a23d$2cba5bc0$a100a8c0@mchasecompaq> From: "Michael A Chase" To: "Robert Collins" , "Cygwin-Apps" References: <20020118180305 DOT GA2312 AT dothill DOT com> <0a3501c1a074$07c97be0$0200a8c0 AT lifelesswks> <001401c1a237$c1ebc680$a100a8c0 AT mchasecompaq> Subject: Low-level progress messages in setup.log Date: Sun, 20 Jan 2002 21:33:30 -0800 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 log() appears to be called for a lot of progress messages without LOG_BABBLE. This causes the messages to be saved in both setup.log and setup.log.full. "io_stream::~io_stream called" in io_stream.cc in particular adds a lot of bulk to setup.log. I think I can identify many of those low-level progress messages that would be better not included in setup.log. Would you be interested in a patch? -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age.