Hello!

Lukas already imported most of our patches. I merged this modified
upstream into our "master" branch and looked at the remaining
differences.

"slow sync: avoid empty anchors, that confuses ScheduleWorld" - I
reverted that because it is no longer needed.

"autotools: added synthesis.pc file for pkg-config",
"Linux timezones: compile fix for libecal and
--disable-evolution-compatibility", "Linux timezones: previous fix for
icalcomponent_as_ical_string_r was incomplete" - could be merged into
synthesis.ch.

The discussion about "client + statistics workaround: treat status 200
as 201 for Replace cmd (which is really an Add)" is on-going between
Lukas and Congwu, which is great because I can lay back and watch the
discussion without having to worry about it ;-) For the time being I'll
keep it in our tree.

I wonder a bit what we should do about obsolete code. If a branch was
not merged yet, then it is hard to see whether that is because it was
rejected (my original "logging" branch) or still pending (Congwu's
"Client+Resend data: bug#3427, add sysync::STEP_RESENDDATA").

I suggest that we purge obsolete code from the public repos. If someone
wants to retain a copy for himself, then this is possible in a cloned
repo.

Candidates for removal are:
      * "logging", "logging_upstream", "mobical" branches in the
        syncevolution repo (the latter was merged into synthesis
        upstream)
      * "remote-rules" in the synthesis repo
      * the "Mimedirprofile: allow parameter value enclosed by double
        quote for vcard2.1" patch in the yongsheng branch

Finally, I'd like to see the san.[h|cpp] code be moved into
src/sysync_SDK/Sources because it needs to be called by its users
directly. I can't do this myself because implies a license change (LGPL
-> BSD) and thus has to be done by the owners.

-- 
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.



_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis

Reply via email to