Hello Patrick,
I'm about to review merge the patches from the moblin/master branch into our
libsynthesis repo - thanks to your earlier cleanup of the history it's a really
straightforward task, thanks for that!
The only change that I'm not sure about is:
71aef21545
On Mi, 2010-01-27 at 11:03 +, Lukas Zeller wrote:
I'm about to review merge the patches from the moblin/master branch
into our libsynthesis repo - thanks to your earlier cleanup of the
history it's a really straightforward task, thanks for that!
The only change that I'm not sure about
Hi Patrick,
thanks for the comments.
On Jan 27, 2010, at 12:24 , Patrick Ohly wrote:
Second - I don't really see why declaring it static would mean
anything for initialisation (apart from the fact that gcc seems not to
be able to figure out it should complain about it then) - C-ish stuff
is
On Mi, 2010-01-27 at 11:50 +, Lukas Zeller wrote:
On Jan 27, 2010, at 12:24 , Patrick Ohly wrote:
Second - I don't really see why declaring it static would mean
anything for initialisation (apart from the fact that gcc seems not to
be able to figure out it should complain about it
Hello Patrick,
On Jan 26, 2010, at 17:38 , Patrick Ohly wrote:
As I might have mentioned before, in SyncEvolution we try to prevent
unwanted slow syncs to give the user the chance to choose some other way
of recovery (refresh sync, restore from backup):
On Mi, 2010-01-27 at 16:44 +, Lukas Zeller wrote:
What about datastoreinitscript or maybe initscript? These are
called before user data is accessed the first time, which would be
early enough to stop the whole thing if needed, but late enough to be
sure the sync mode is known. BTW: I
Timezone mapping is behaving little weird , For the same Buenos Aire meeting
which I created logs and sent last week was mapped to Africa/Harare, now same
event getting mapped to Standard Time/Daylight Savings Time 1.
I stepped through the code and in the TIMEZONEtoInternal function has
