To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52150
User hjs 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=52150
User hjs 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=52150
--- Additional comments from [EMAIL PROTECTED] Tue Jul 19 07:19:11 -0700
2005 ---
Having the filestamps in the patches did help us in the past to recover from
mangle
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52150
--- Additional comments from [EMAIL PROTECTED] Tue Jul 19 05:49:18 -0700
2005 ---
Why do even the timestamps of files change, which weren't modified in this
round? T
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52150
--- Additional comments from [EMAIL PROTECTED] Tue Jul 19 04:42:13 -0700
2005 ---
ause: better history is in CVS...
---
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52150
--- Additional comments from [EMAIL PROTECTED] Tue Jul 19 04:15:44 -0700
2005 ---
in "tg_ext.mk", all *ix platforms now use GNUPATCH. cygwin tools contain
gnupatch a
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52150
User pjanik changed the following:
What|Old value |New value
=
