--- Comment #19 from pohly <patrick.ohly(a)intel.com> 2010-04-27 06:08:51 PDT ---
(In reply to comment #18)
> and add forced types to the testing.
Done. Congwu, do you agree with the following patch? Ready to merge mbc1197
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Tue Apr 27 14:59:33 2010 +0200
syncevo-phone-config: add "forced types" to tested configs (MBC #1197)
Types like "text/calendar" are implicitly turned into
"text/x-vcalendar" inside SyncEvolution when asking the phone to
sync. Forcing the type leads to a different SAN message and thus
is worth testing.
Forcing legacy types also leads to a slightly different sync session:
the SAN is the same as without forcing the type, but then we send
simpler CtCap information. This might make a difference when a phone
stumbles over too complex CtCap. But because such a phone should
work when disabling CtCap altogether, the forced legacy types are
not tested separately (would increase overall number of test cases).
Using --advanced with a --type for which no test data exists now fails
with an error instead of silently using empty items.
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.