To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User fs changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User asarkar changed the following:
What|Old value |New value
=
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
--- Additional comments from [EMAIL PROTECTED] Mon Oct 17 23:27:30 -0700
2005 ---
Then feel free to introduce a target milestone Danube-S, apply it to this issue
and
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
--- Additional comments from [EMAIL PROTECTED] Mon Oct 17 17:54:09 -0700
2005 ---
According to engineering this should get resolved in Danube-S. Starting 3.x,
CEE us
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
--- Additional comments from [EMAIL PROTECTED] Wed Apr 27 02:18:04 -0700
2005 ---
To avoid grief in the future I would once more recommend to use test cases as
close
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User asarkar changed the following:
What|Old value |New value
=
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User st changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User asarkar changed the following:
What|Old value |New value
=
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=1950
User asarkar changed the following:
What|Old value |New value
=
