To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=59372
User vq changed the following:
What |Old value |New value
================================================================================
Priority|P2 |P3
--------------------------------------------------------------------------------
Target milestone|OOo 2.0.2 |DevTools
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu Dec 15 04:05:07 -0800
2005 -------
@rt: No, but I thought hr is. I aggree that this is not a P2 and that one can
work around this problem. I basically already did what you said and vq24 is IMHO
good to go.
@hr: I also think this is just a sub-optimal warning. The *_ANCHOR tag doesn't
have a real meaning for binary files so cwsresync could as well move the
*_ANCHOR
tag to the desired milestone, keep the current version (not merging) from the
CWS
and issue this warning. Maybe it should be changed to this:
Resyncing 'fooo.bar' (1.5-1.6): binary file has been changed in
CWS and in MWS. Moving ANCHOR tag, keeping current cws version. Please check!.
---------------------------------------------------------------------
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]
