Patrick,
looks fine to me :-).
No objections, I agree to them.
Thanks,
Beat
On Tue, 2009-07-28 at 18:33 +0100, Beat Forster wrote:
I'd prefer the 2nd way. However let me have a
look first to get an impression about
implications.
I gave it a try. The amount of changes in existing code is fairly small,
but it was necessary to introduce two new functions with more fuzzy line
end matching. See attached patches. The first one is unrelated to the
problem, I only changed it because I was going to touch the code anyway.
Please let me know what you think. I tested it with \n VTIMZONE
definitions and \r\n, both gave the same result.
I'd like to include this fix in SyncEvolution 0.9 together with the
EXDATE workaround in the XML config. Ideally I'll commit both to the
master branches so that it can get included in the upcoming nightly
testing.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
Attachment converted:
bfo:0001-vtimezone-use#248E9E.patch ( / )
(00248E9E)
Attachment converted:
bfo:0002-timezone-pars#248E9F.patch ( / )
(00248E9F)
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
--
-----------------------------------------------
Beat FORSTER
Dipl. El. Ing. ETH
Dipl. NDS ETHZ in Betriebswissenschaften
Managing Partner
[email protected]
Synthesis AG SyncML Server & Client Solutions
Badenerstrasse 18, CH-8004 Zürich, Switzerland
Tel (direct): +41 44 440 66 02
Fax: +41 44 440 66 04
email: [email protected]
web: http://www.synthesis.ch
-----------------------------------------------
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
