On Sat, 2007-12-22 at 02:37 +0100, Guido Diepen wrote:
> > Patch away! Anything to lose error messages like these is a good
> > thing :)
>
> Again, since multiple people are using the sync-engine regularly and I don't
> want to commit something that will break the code, I supply the patch
> manually. The reason for this is that i just started last week with python
> and I want to be sure that what is svn still keeps working ;) I am pretty
> sure that it is, but since I currently really need the exchange partnership
> not to be deleted, I can't fully test it right now (i did some preliminary
> tests with added return statements in the device_(dis)connect_cb functions
> and they seemed to work without a problem). I will test that exchange
> partnership problem later on for you though :)
>
> Could you verify the attached patch and if it is working, could you either
> notify me, and I will feel free to commit it :), or commit it yourself,
> whatever is the easiest for you.
>
Looks basically sane and seems to work well here! Thanks for that patch,
I have committed it in r3115 along with a little fix that should stop
Exchange server partnerships being clobbered - if you could verify this
at your end I would be grateful, also let me know if you see any adverse
effects.
Now I just need to find a way to stop Opensync cleanly if a user tries
to start one without either odccm running or a device connected. This
should be straightforward with Opensync 0.3x but is a bit more
problematic with the earlier versions....
John.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SynCE-Devel mailing list
SynCE-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synce-devel
