To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=48031
------- Additional comments from [EMAIL PROTECTED] Sat Apr 23 13:37:05 -0700 2005 ------- In fact nativefixer6 is a good example: [EMAIL PROTECTED]:~> cwsquery -m SRC680 -c nativefixer6 modules cwsquery -- version: 1.5 cwsquery: Master workspace 'SRC680', child workspace 'nativefixer6': cwsquery: Modules: setupso_native instset_native sysui instset_cso_native instsetoo_native setup_native solenv tab scp2so shell sysui_so sal scp2 -> we have a way to get the list of all modules in that cws. There are both SO and OO modules. Why not separate changes in SO modules in other cws and make it private? [EMAIL PROTECTED]:~> cwsquery -m SRC680 -c nativefixer6 taskids cwsquery -- version: 1.5 cwsquery: Master workspace 'SRC680', child workspace 'nativefixer6': cwsquery: Task ID(s): 121395 121721 b6186553 i46317 i46961 i42173 i46850 i45628 121397 b6243124 b6244608 i46226 b6243141 i46530 b6250018 121279 i47641 b6247995 b6251160 i46741 b6248614 121396 b6250102 i45148 b6243085 i46536 b6243100 121277 b6254678 b6251455 i46982 -> we have a list of all issues. Some of them are IZ, some of them in Sun internal bug tracking system. So why can't we see this child workspace in EIS with public data available? We do not care about changes in SO-only modules. We do not care about SO-only issues. We care about public data. --------------------------------------------------------------------- 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]
