To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=84497
------- Additional comments from [EMAIL PROTECTED] Wed Sep 24 20:31:09 +0000 2008 ------- @rt: yep, loosely followed that. As a developer, being one of the main targets of build system output, I concur with Kay - I just need info about the file that currently gets compiled, no frills. Tar output & install sets are minor issues IMO, as they represent only fractions of normal build logs. What I'm after is, the patch here improves things a lot for me (it might even do what you suggested for the verbose=false case - *not* logging anything per compiled file is clearly not want I want), so why not taking this as a step in the right direction & integrate it (or put it into one of the *shutup CWS)? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
